This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
Re: target/8087: sparc-sun-solaris2.7 C testsuite failures in execute/20020720-1.c w/-m64 or on sparcv9/sparc64
- From: davem at gcc dot gnu dot org
- To: gcc-bugs at gcc dot gnu dot org, gcc-prs at gcc dot gnu dot org, ghazi at caip dot rutgers dot edu, nobody at gcc dot gnu dot org, rth at redhat dot com, davem at redhat dot com, jakub at redhat dot com, roger at eyesopen dot com
- Date: 30 Sep 2002 22:52:04 -0000
- Subject: Re: target/8087: sparc-sun-solaris2.7 C testsuite failures in execute/20020720-1.c w/-m64 or on sparcv9/sparc64
- Reply-to: davem at gcc dot gnu dot org, gcc-bugs at gcc dot gnu dot org, gcc-prs at gcc dot gnu dot org, ghazi at caip dot rutgers dot edu, nobody at gcc dot gnu dot org, rth at redhat dot com, davem at redhat dot com, jakub at redhat dot com, roger at eyesopen dot com, gcc-gnats at gcc dot gnu dot org
Synopsis: sparc-sun-solaris2.7 C testsuite failures in execute/20020720-1.c w/-m64 or on sparcv9/sparc64
State-Changed-From-To: open->analyzed
State-Changed-By: davem
State-Changed-When: Mon Sep 30 15:52:04 2002
State-Changed-Why:
The problem is, it's REALLY REALLY expensive to set the
float condition codes to a constant value (two FPU synchronizing memory operations).
If I implement these patterns, will they actually be output
ever?
I think it's really totally silly to require a backend
to implement these patterns. I can think of a few other
platforms where this is quite expensive.
Is there some way to remove the requirement?
Has the compiler documentation been updated to reflect
this new pattern requirement?
http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=8087