Tobias Burnus wrote:
> Toon Moene wrote:
Can somebody with access to SPEC sources confirm / deny and file a bug
report, if appropriate?
I just started working on SPEC CPU2006 issues this week.
> Seemingly yes. To a certain extend this was by accident as "-msse3" was
> used, but it is on
Toon Moene wrote:
>>> Can somebody with access to SPEC sources confirm / deny and file a bug
>>> report, if appropriate?
>>
>> It is an x87 bug only and has already been filed:
>> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39856 and working on
>> being fixed already.
The reason that is was not f
Andrew Pinski wrote:
On Sat, Apr 25, 2009 at 7:02 AM, Thomas Koenig wrote:
Can somebody with access to SPEC sources confirm / deny and file a bug
report, if appropriate?
It is an x87 bug only and has already been filed:
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39856 and working on
bein
Thomas Koenig wrote:
> Hello world,
>
> http://www.heise.de/newsticker/GCC-4-4-0-erschienen--/meldung/136529
>
> reports the release of gcc 4.4.0 and also claims that 453.povray from
> SPEC CPU 2006 caused an ICE in g++. The tone of the report is fairly
> negative.
They accused us of a too-ha
On Sat, Apr 25, 2009 at 7:02 AM, Thomas Koenig wrote:
> Can somebody with access to SPEC sources confirm / deny and file a bug
> report, if appropriate?
It is an x87 bug only and has already been filed:
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39856 and working on
being fixed already.
Thanks
Hello world,
http://www.heise.de/newsticker/GCC-4-4-0-erschienen--/meldung/136529
reports the release of gcc 4.4.0 and also claims that 453.povray from
SPEC CPU 2006 caused an ICE in g++. The tone of the report is fairly
negative.
Can somebody with access to SPEC sources confirm / deny and file
