Alex Ionescu wrote:
1) 64-bit pointer bug: I asked Thomas to make a
test-case and submit it. I
don't know if he has.
I hope so. So it disappears in time.
2) Pragma support: GCC doesn't view
msvc-compatibility as a priority.
Ok why. Microsoft does not take Gcc compatibility as a priority. MSVC
does not support gcc Pragma's either. But gcc is being good and
supporting _pragma from C99 allowing more flexable handling.
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
Please take a closer look at what 4.2 is truly doing. Double set of
builtins. -mrtd is swaping the builtins. The last post of so called
problem is the expected result. With -mrtd you have stdcall builtins.
Without you have cdecl. There are options where this can be still
forced to be cdecl or stdcall only for builtins and that would give the
result a lot of people would expect or inversed to what people expect.
In theory with a bit of tweeking cdecl and stdcall for builtin calls
could be made perfectly acceptable since they are both there.
gcc version 3.4 20030130 (experimental) << mingw trash missing the
double set of builtins and the other fix to -mrtd to be correct half of
the double buildin patches and many other strange errors caused by mingw
own runtime files.
As I said it was fixed. I did not say it was fixed how everyone expected.
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.
Gcc is not alone with Vista Bugs. Firefox had about 100 regarding
vista.. Microsoft worked on fixing them. Funny bit Microsoft
developers are working on fixing some of the Vista bugs in gcc.
4.2 is known to have errors still a work in progress. So nothing to
say if PSEH will or will not work in final release yet. No point
jumping gun.
4.2 is a fairly large upgrade. Lots of important alterations. Price
lot of havoc.
This is part of the problem of mingw. Lot of the versions are build
from experimental versions then patches applied. And worst bit halfway
threw a patch set being applied in a lot of cases. Just think for one
minute some of the problems Reactos has when that is done.
Problem with gcc experimental versions they have not been threw the
final bug squashing process. I am more trusting of a gcc if patchs from
the experimental version has been hand picked. and applied to a stable
version. At least weakness as kept to a limited number of places and a
complete set should be extracted as a block not getting have a set of
patchs.
Peter Dolding
----------------------------------------------------------------------
Get a free email address with REAL anti-spam protection.
http://www.bluebottle.com