public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Roger Sayle <roger@eyesopen.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 11:46:00 -0000 [thread overview] Message-ID: <20021007184603.18074.qmail@sources.redhat.com> (raw) The following reply was made to PR target/8087; it has been noted by GNATS. From: Roger Sayle <roger@eyesopen.com> To: "David S. Miller" <davem@redhat.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, 7 Oct 2002 12:25:48 -0600 (MDT) > So does sparc32, at different stages of the compilation, for > example for something simple like "double foo(void){return 0.0;}" > the foo.c.00.rtl has: > > (insn 11 10 13 (set (reg/f:SI 109) > (lo_sum:SI (reg:SI 110) > (symbol_ref/u:SI ("*.LLC0")))) -1 (nil) > (expr_list:REG_EQUAL (symbol_ref/u:SI ("*.LLC0")) > (nil))) > > Which has the SYMBOL_REG inside of a LO_SUM construct. Indeed. The difference is that by foo.c.18.combine the constant pool reference has been optimized away on sparc32, but it isn't if "-m64" is specified or on sparc64. > Note, the "/u" flag means unchanging which means it is > a constant pool SYMBOL_REF. Thanks. > A possible fix may be to extend this test is also allow the constant > pool to be indexed via LO_SUM. Something like: > > This looks perfectly fine to me. I think it will improve code > on all platforms that use LO_SUM, not just sparc64 and sparc32. Excellent. I'll perform the usual bootstraps and regression tests on sparc-sun-solaris2.8, and then post the patch to gcc-patches today or tomorrow. Roger --
next reply other threads:[~2002-10-07 18:46 UTC|newest] Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-10-07 11:46 Roger Sayle [this message] -- strict thread matches above, loose matches on Subject: below -- 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 David S. Miller 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=20021007184603.18074.qmail@sources.redhat.com \ --to=roger@eyesopen.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: linkBe 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).