public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/45633] [4.6 regression] internal compiler error: verify_stmts failed
Date: Tue, 14 Sep 2010 17:16:00 -0000 [thread overview]
Message-ID: <20100914171559.4128.qmail@sourceware.org> (raw)
In-Reply-To: <bug-45633-13856@http.gcc.gnu.org/bugzilla/>
------- Comment #8 from jakub at gcc dot gnu dot org 2010-09-14 17:15 -------
I've looked at the combiner with the second patch, but I'm afraid this isn't
fixable in the combiner easily. While combiner is able for i3
(set (reg:V2DI res) (plus:V2DI (reg:V2DI temp) (mem:V2DI (symbol_ref:P t))))
, i2
(set (reg:V2DI temp) (minus:V2DI zero) (mem:V2DI (reg:V2DI a)))
and i1
(set (reg:V2DI zero) (const_vector:V2DI [0 0]))
to figure this is
(set (reg:V2DI res) (minus:V2DI (mem:V2DI (symbol_ref:P t)) (reg:V2DI a))
(plus repeating i1, as its result is not dead), this pattern doesn't match
as minus obviously isn't commutative and combiner doesn't try to make 3 insns
out of 3. So I'd prefer if we could either apply the first patch, or try TER
on the PLUS_EXPR to see if the second operand isn't negation and expand it as
MINUS_EXPR, even when MINUS_EXPR isn't allowed on such arguments in GIMPLE.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45633
next prev parent reply other threads:[~2010-09-14 17:16 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-10 11:18 [Bug tree-optimization/45633] New: " jojelino at gmail dot com
2010-09-10 11:20 ` [Bug tree-optimization/45633] " jojelino at gmail dot com
2010-09-10 11:29 ` rguenth at gcc dot gnu dot org
2010-09-10 12:13 ` jojelino at gmail dot com
2010-09-11 20:59 ` jojelino at gmail dot com
2010-09-14 15:24 ` jakub at gcc dot gnu dot org
2010-09-14 16:18 ` jakub at gcc dot gnu dot org
2010-09-14 16:20 ` jakub at gcc dot gnu dot org
2010-09-14 17:16 ` jakub at gcc dot gnu dot org [this message]
2010-09-14 18:43 ` jakub at gcc dot gnu dot org
2010-09-15 15:43 ` jakub at gcc dot gnu dot org
2010-09-15 16:06 ` jakub at gcc dot gnu dot org
[not found] <bug-45633-4@http.gcc.gnu.org/bugzilla/>
2015-02-05 23:45 ` law at redhat dot com
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=20100914171559.4128.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: 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).