public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "amacleod at redhat dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/30604] Unable to coalesce ssa_names <x> and <y> which are marked as MUST COALESCE
Date: Mon, 12 Mar 2007 13:34:00 -0000 [thread overview]
Message-ID: <20070312133341.20289.qmail@sourceware.org> (raw)
In-Reply-To: <bug-30604-3639@http.gcc.gnu.org/bugzilla/>
------- Comment #10 from amacleod at redhat dot com 2007-03-12 13:33 -------
They do all have the (ab) next to them, I was just indicating that they all
occurred in a PHI together, and hence needed to be coalesced. I should have
been more precise.
Well, _t_3 definately does have the (ab) flag, and I don't know what all it
does do, but it does introduce the situation where we have overlapping abnormal
ssa-names which have to be coalesced.
I see it does a bunch of replacements which include _t_3(ab), lines such as:
Replaced (struct *) #ref#17#7_8338 with _t_3(ab) in #ref#17#7.2741_8343 =
(struct *) #ref#17#7_8338;
(Just an example, not meant to be the erroneous replacement). So it is clearly
doing something with it.
--
amacleod at redhat dot com changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |amacleod at redhat dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30604
next prev parent reply other threads:[~2007-03-12 13:34 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-26 20:29 [Bug tree-optimization/30604] New: " mark at gcc dot gnu dot org
2007-01-26 20:35 ` [Bug tree-optimization/30604] " mark at gcc dot gnu dot org
2007-01-28 19:26 ` pinskia at gcc dot gnu dot org
2007-02-01 15:01 ` aph at gcc dot gnu dot org
2007-02-01 15:23 ` mark at gcc dot gnu dot org
2007-03-08 9:04 ` tbm at cyrius dot com
2007-03-08 9:05 ` tbm at cyrius dot com
2007-03-08 12:34 ` pinskia at gcc dot gnu dot org
2007-03-08 20:12 ` amacleod at redhat dot com
2007-03-10 0:01 ` Daniel Berlin
2007-03-08 20:21 ` amacleod at redhat dot com
2007-03-10 0:02 ` dberlin at dberlin dot org
2007-03-12 13:34 ` amacleod at redhat dot com [this message]
2007-11-09 15:37 ` amacleod at redhat dot com
2007-11-09 18:27 ` pinskia at gcc dot gnu dot org
2007-11-09 18:41 ` amacleod at redhat dot com
2008-02-15 12:56 ` rguenth at gcc dot gnu dot org
[not found] <bug-30604-4@http.gcc.gnu.org/bugzilla/>
2013-06-06 8:59 ` dcb314 at hotmail dot com
2013-06-06 9:51 ` rguenther at suse dot de
2020-07-28 2:04 ` asolokha at gmx dot com
2020-07-28 5:54 ` rguenth 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=20070312133341.20289.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).