public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "davem at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/52684] [4.7 regression] glibc long double math tests fail on sparc 64-bit
Date: Tue, 01 May 2012 22:44:00 -0000	[thread overview]
Message-ID: <bug-52684-4-GNK1rfCHAc@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-52684-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52684

--- Comment #4 from davem at gcc dot gnu.org 2012-05-01 22:44:08 UTC ---
Ok, I see why 32-bit works.  On 32-bit we use real libfuncs in the optabs, so
the compiler can see all the typing information and emit the proper information
to stick into the CALL_INSN_FUNCTION_USAGE lists.

But when we emit soft TFmode libcalls by hand, as on 64-bit, this information
is lost.  So DSE has nothing to work with and can't see that the temporary
stack slots are inputs to the libcall.

We'll have to tack on our own reg use notes by hand in functions like
emit_soft_tfmode_libcall() and sparc_emit_float_lib_cmp().


  parent reply	other threads:[~2012-05-01 22:44 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-23  8:52 [Bug target/52684] New: " davem at gcc dot gnu.org
2012-03-23  9:07 ` [Bug target/52684] " davem at gcc dot gnu.org
2012-04-29 20:49 ` davem at gcc dot gnu.org
2012-04-29 22:09 ` [Bug target/52684] [4.7 regression] " ebotcazou at gcc dot gnu.org
2012-05-01 22:27 ` davem at gcc dot gnu.org
2012-05-01 22:44 ` davem at gcc dot gnu.org [this message]
2012-05-01 23:13 ` davem at gcc dot gnu.org
2012-05-02  7:01 ` davem at gcc dot gnu.org
2012-05-02  7:02 ` davem at gcc dot gnu.org
2012-05-02  7:24 ` davem at gcc dot gnu.org
2012-05-02  8:10 ` davem at gcc dot gnu.org
2012-05-03  5:18 ` davem at gcc dot gnu.org
2012-05-03 22:20 ` davem at gcc dot gnu.org
2012-05-03 22:35 ` davem at gcc dot gnu.org
2012-05-03 22:55 ` davem at gcc dot gnu.org

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=bug-52684-4-GNK1rfCHAc@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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).