public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "kazu at cs dot umass dot edu" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug optimization/14541] New: [tree-ssa] gcc.dg/torture/builtin-explog-1.c fails Date: Fri, 12 Mar 2004 00:17:00 -0000 [thread overview] Message-ID: <20040312001701.14541.kazu@cs.umass.edu> (raw) Here is a reduced testcase. Basically, link_error won't go away. This testcase works on mainline, so this is a regression. extern double log (double); extern double exp (double); extern void link_failure (void); void test (double d1) { if (log (exp (d1)) != d1) link_failure (); } int main (void) { return 0; } -- Summary: [tree-ssa] gcc.dg/torture/builtin-explog-1.c fails Product: gcc Version: tree-ssa Status: UNCONFIRMED Keywords: pessimizes-code Severity: normal Priority: P2 Component: optimization AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: kazu at cs dot umass dot edu CC: gcc-bugs at gcc dot gnu dot org GCC target triplet: h8300-elf http://gcc.gnu.org/bugzilla/show_bug.cgi?id=14541
next reply other threads:[~2004-03-12 0:17 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2004-03-12 0:17 kazu at cs dot umass dot edu [this message] 2004-03-12 0:18 ` [Bug optimization/14541] " kazu at cs dot umass dot edu 2004-03-12 0:26 ` pinskia at gcc dot gnu dot org 2004-03-12 2:40 ` [Bug optimization/14541] [tree-ssa] built-in math functions are not fully optimized at tree level kazu at cs dot umass dot edu 2004-03-12 15:30 ` amacleod at redhat dot com 2004-03-25 0:09 ` bje at gcc dot gnu dot org 2004-05-03 12:37 ` pinskia at gcc dot gnu dot org 2004-05-04 7:56 ` kazu at cs dot umass dot edu 2004-05-04 11:32 ` pinskia at gcc dot gnu dot org 2004-05-04 15:52 ` kazu at cs dot umass dot edu 2004-05-04 15:57 ` pinskia at gcc dot gnu dot org 2004-05-24 21:48 ` [Bug tree-optimization/14541] " pinskia at gcc dot gnu dot org 2004-06-01 1:47 ` pinskia at gcc dot gnu dot org 2004-06-21 5:15 ` pinskia at gcc dot gnu dot 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=20040312001701.14541.kazu@cs.umass.edu \ --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: 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).