public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/47312] [4.6 Regression] ICE: in expand_ternary_op, at optabs.c:656 with -flto -mno-sse -mxop and __builtin_fmaf()
Date: Mon, 17 Jan 2011 15:54:00 -0000 [thread overview]
Message-ID: <bug-47312-4-qGc8Yw8GHG@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-47312-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47312
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jakub at gcc dot gnu.org
--- Comment #1 from Jakub Jelinek <jakub at gcc dot gnu.org> 2011-01-17 15:46:52 UTC ---
With LTO, relying on FMA_EXPR being present in the IL only iff target supports
it is IMHO wrong, because using slightly different options between cc1 and lto1
can result in optab_handler (fma_optab, mode) == CODE_FOR_nothing even when
FMA_EXPR is present in the IL. I'd say we should expand FMA_EXPR as
__builtin_fma in that case. Richi, do you agree?
next prev parent reply other threads:[~2011-01-17 15:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-16 3:14 [Bug target/47312] New: " zsojka at seznam dot cz
2011-01-17 13:52 ` [Bug target/47312] " rguenth at gcc dot gnu.org
2011-01-17 15:54 ` jakub at gcc dot gnu.org [this message]
2011-01-19 21:29 ` jakub at gcc dot gnu.org
2011-02-02 15:24 ` jakub at gcc dot gnu.org
2011-02-02 15:31 ` rguenth at gcc dot gnu.org
2011-02-02 15:39 ` jakub at gcc dot gnu.org
2011-02-03 10:53 ` jakub at gcc dot gnu.org
2011-02-03 11:00 ` jakub 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-47312-4-qGc8Yw8GHG@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).