public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: davem@gcc.gnu.org To: gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, ghazi@caip.rutgers.edu, nobody@gcc.gnu.org, rth@redhat.com, davem@redhat.com, jakub@redhat.com, roger@eyesopen.com Subject: Re: target/8087: sparc-sun-solaris2.7 C testsuite failures in execute/20020720-1.c w/-m64 or on sparcv9/sparc64 Date: Mon, 30 Sep 2002 15:52:00 -0000 [thread overview] Message-ID: <20020930225204.8517.qmail@sources.redhat.com> (raw) 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
next reply other threads:[~2002-09-30 22:52 UTC|newest] Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-09-30 15:52 davem [this message] -- strict thread matches above, loose matches on Subject: below -- 2002-10-07 11:46 Richard Henderson 2002-10-07 11:46 Roger Sayle 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:26 David S. Miller 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-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=20020930225204.8517.qmail@sources.redhat.com \ --to=davem@gcc.gnu.org \ --cc=davem@redhat.com \ --cc=gcc-bugs@gcc.gnu.org \ --cc=gcc-gnats@gcc.gnu.org \ --cc=gcc-prs@gcc.gnu.org \ --cc=ghazi@caip.rutgers.edu \ --cc=jakub@redhat.com \ --cc=nobody@gcc.gnu.org \ --cc=roger@eyesopen.com \ --cc=rth@redhat.com \ /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).