public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jamborm at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/40432] [4.5 Regression] verify_stmts failed with -O2: non-register as LHS of unary operation
Date: Sun, 14 Jun 2009 04:55:00 -0000 [thread overview]
Message-ID: <20090614045506.463.qmail@sourceware.org> (raw)
In-Reply-To: <bug-40432-9596@http.gcc.gnu.org/bugzilla/>
------- Comment #3 from jamborm at gcc dot gnu dot org 2009-06-14 04:55 -------
(In reply to comment #1)
> I want to say the SRA changes caused this ...
>
Yes it did. I can reproduce it and it should not be difficult to
fix. However, I'll have a look at why SRA constructs such a statement
in the first place. The code that does it currently things it's
either appending ".eh" to the LHS or the VCE to the RHS, not both.
But maybe it's just an oversight, I'll check in the morning.
--
jamborm at gcc dot gnu dot org changed:
What |Removed |Added
----------------------------------------------------------------------------
AssignedTo|unassigned at gcc dot gnu |jamborm at gcc dot gnu dot
|dot org |org
Status|UNCONFIRMED |ASSIGNED
Ever Confirmed|0 |1
Last reconfirmed|0000-00-00 00:00:00 |2009-06-14 04:55:06
date| |
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=40432
next prev parent reply other threads:[~2009-06-14 4:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-12 18:55 [Bug c/40432] New: " dcb314 at hotmail dot com
2009-06-12 18:57 ` [Bug tree-optimization/40432] [4.5 Regression] " pinskia at gcc dot gnu dot org
2009-06-12 18:58 ` dcb314 at hotmail dot com
2009-06-14 4:55 ` jamborm at gcc dot gnu dot org [this message]
2009-06-15 9:09 ` jamborm at gcc dot gnu dot org
2009-06-16 9:57 ` jamborm at gcc dot gnu dot org
2009-06-16 10:17 ` jamborm at gcc dot gnu dot org
2009-06-16 10:24 ` jamborm 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=20090614045506.463.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).