public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/43783] [4.5/4.6 regression] -O -ftree-pre options compile libbid wrong Date: Mon, 19 Apr 2010 11:03:00 -0000 [thread overview] Message-ID: <20100419110300.11866.qmail@sourceware.org> (raw) In-Reply-To: <bug-43783-17259@http.gcc.gnu.org/bugzilla/> ------- Comment #5 from rguenth at gcc dot gnu dot org 2010-04-19 11:02 ------- It's not bid128_ext_fma that is miscompiled but bid_round.c, building that with -O1 [-ftree-pre] works [fails]. __bid_round192_39_57 is miscompiled by PRE. -- rguenth at gcc dot gnu dot org changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|unassigned at gcc dot gnu |rguenth at gcc dot gnu dot |dot org |org Status|NEW |ASSIGNED Last reconfirmed|2010-04-19 09:56:21 |2010-04-19 11:02:59 date| | http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43783
next prev parent reply other threads:[~2010-04-19 11:03 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2010-04-18 15:53 [Bug tree-optimization/43783] New: [4.5 " roman at binarylife dot net 2010-04-18 18:22 ` [Bug tree-optimization/43783] " rguenth at gcc dot gnu dot org 2010-04-18 18:34 ` roman at binarylife dot net 2010-04-19 4:25 ` roman at binarylife dot net 2010-04-19 9:56 ` [Bug tree-optimization/43783] [4.5/4.6 " rguenth at gcc dot gnu dot org 2010-04-19 11:03 ` rguenth at gcc dot gnu dot org [this message] 2010-04-19 11:20 ` rguenth at gcc dot gnu dot org 2010-04-19 11:57 ` rguenth at gcc dot gnu dot org 2010-04-19 13:37 ` rguenth at gcc dot gnu dot org 2010-04-19 20:46 ` [Bug tree-optimization/43783] [4.5 Regression] " roman at binarylife dot net 2010-04-20 9:06 ` rguenth at gcc dot gnu dot org 2010-04-20 9:06 ` rguenth 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=20100419110300.11866.qmail@sourceware.org \ --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).