1) 64-bit pointer bug: I asked Thomas to make a test-case and submit it. I don't know if he has. 2) Pragma support: GCC doesn't view msvc-compatibility as a priority. 3) -mrtd: Has been fixed and re-broken countless times. This is an example of one of them: http://gcc.gnu.org/bugzilla/show_bug.cgi?id=9601. Still present in 4.2 4) One of multiple Vista bugs: http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30335.
There's also the fact that 4.1.2+ are unusuable on -j2 or more because they incorrectly map PCH files, so our build server is forced to use 3.4.5, which is incompatible with KJK's new PSEH. 4.2 is also incompatible with PSEH due to other, newly added exciting bugs.
-----Original Message----- From: ros-dev-bounces@reactos.org [mailto:ros-dev-bounces@reactos.org] On Behalf Of Steven Edwards Sent: April-25-07 12:15 PM To: ReactOS Development List Subject: Re: [ros-dev] [ros-diffs] [dgorbachev] 26483: Undo r26482 change, waste more stack space.
On 4/25/07, Alex Ionescu ionucu@videotron.ca wrote:
Besides, just like Windows has a very strong internal architecture and at its core is a remarkable OS, so is GCC as a compiler. Some of its
developers
are true compiler designers and some work for large companies, many of
which
even hold and license patents to GCC. The optimizer in GCC is very
powerful
and can even rival MSVC in some cases. The cases where it doesn't cause a bug. Because this *is* the problem behind GCC! It's a remarkable, powerful and portable compiler, yet it is unreliable and sometimes downright
stupid.
Recall your unsuccessful warnings patch to emulate MSVC. Recall the 64-bit pointer bug I discovered. Recall the the lack of useful pragmas that other compilers support. Recall the inability to use STDCALL as default which means Fireball had to spend a week to "convert" a DDK sample to ReactOS
and
which makes *any* DDK code uncompilable by GCC (purposeful sabotage?). Recall the register allocation bug 2 years ago which used ebx *before*
push
ebx to save it, and I can name more.
If you point out the bug numbers in question I'd be happy to pester the gcc team. I won't file a bug report for these issues as I don't know enough about them but get me a list with bugzilla IDs and I will at least spam them for a while.