Gcc4 issues
Dan Kegel
dank@kegel.com
Sun Mar 27 15:47:00 GMT 2005
Arno Schuring wrote:
>>> It's i686, so primary target and as such will get the most testing,
>>> but so far I have only encountered one segfault (python 2.4 make
>>> check) and two ICEs, one during the build of X.org and one building
>>> Enlightenment DR17.
>>> (and a double-free warning in mke3fs)
>>
>> Not bad! Have they fixed the ICEs yet?
>
> One is fixed, the other had a proposed fix which had some nasty side
> effects. I believe that one is still open. It made me feel bad about
> reporting it without being able to help fix it...
>
> (it's http://gcc.gnu.org/bugzilla/show_bug.cgi?id=20491)
Oooh, good catch. Thanks to people like you
for helping make sure gcc-4.0's release is done
with eyes wide open and as many bugs fixed as
possible.
I'm busy redoing crosstool's rpm packaging scheme
(gee, turns out SRPMS are kind of a must if you
want sysadmins to take it seriously), but as soon
as I'm done with that, I hope to try gcc-4.0
on a bunch of code and see if I can break it
like you've been doing.
- Dan
--
Trying to get a job as a c++ developer? See http://kegel.com/academy/getting-hired.html
------
Want more information? See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/
Want to unsubscribe? Send a note to crossgcc-unsubscribe@sources.redhat.com
More information about the crossgcc
mailing list