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.