public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: "David S. Miller" <davem@redhat.com>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: target/8087: sparc-sun-solaris2.7 C testsuite failures in execute/20020720-1.c w/-m64 or on sparcv9/sparc64
Date: Mon, 07 Oct 2002 09:26:00 -0000 [thread overview]
Message-ID: <20021007162601.21101.qmail@sources.redhat.com> (raw)
The following reply was made to PR target/8087; it has been noted by GNATS.
From: "David S. Miller" <davem@redhat.com>
To: roger@eyesopen.com
Cc: davem@gcc.gnu.org, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org,
ghazi@caip.rutgers.edu, rth@redhat.com, jakub@redhat.com,
gcc-gnats@gcc.gnu.org
Subject: Re: target/8087: sparc-sun-solaris2.7 C testsuite failures in
execute/20020720-1.c w/-m64 or on sparcv9/sparc64
Date: Mon, 07 Oct 2002 09:18:51 -0700 (PDT)
From: Roger Sayle <roger@eyesopen.com>
Date: Mon, 7 Oct 2002 10:08:04 -0600 (MDT)
The REG_EQUAL notes is a separate issue. The fixes that I'm still
investigating address the sparc64 backend's convoluted constant
pool loading code.
There is nothing convoluted about it. That's a perfectly valid
and fine way to output a load from the constant pool and expose
all of the instructions to the compiler for scheduling purposes.
It's very complicated to "defer" the full-blown load till later
in the compilatio if that's the idea you have. You have to
force the thing into a register early to get good code and
sane behavior.
Ignoring REG_EQUAL is a bug, and once that bug is fixed the sparc64
"convoluted" constant pool load works as well as "(set reg
(const_double 0.0))"
next reply other threads:[~2002-10-07 16:26 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-07 9:26 David S. Miller [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-10-07 11:46 Roger Sayle
2002-10-07 11:46 Richard Henderson
2002-10-07 11:36 David S. Miller
2002-10-07 11:26 Roger Sayle
2002-10-07 10:26 Kaveh R. Ghazi
2002-10-07 9:26 Roger Sayle
2002-10-07 9:16 Roger Sayle
2002-10-07 9:16 David S. Miller
2002-10-07 0:22 davem
2002-10-03 8:06 Kaveh R. Ghazi
2002-10-02 17:26 David S. Miller
2002-10-02 7:56 Kaveh R. Ghazi
2002-09-30 17:26 Roger Sayle
2002-09-30 16:56 Richard Henderson
2002-09-30 16:36 David S. Miller
2002-09-30 16:26 Richard Henderson
2002-09-30 15:52 davem
2002-09-28 21:46 ghazi
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20021007162601.21101.qmail@sources.redhat.com \
--to=davem@redhat.com \
--cc=gcc-prs@gcc.gnu.org \
--cc=nobody@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).