public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ebotcazou at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ada/65519] [5 regression] unable to coalesce ssa_names 2 and 87 which are marked as MUST COALESCE
Date: Mon, 23 Mar 2015 19:34:00 -0000 [thread overview]
Message-ID: <bug-65519-4-2RY8PH0ndd@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-65519-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65519
Eric Botcazou <ebotcazou at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |rguenth at gcc dot gnu.org
--- Comment #7 from Eric Botcazou <ebotcazou at gcc dot gnu.org> ---
> I don't think that gimple_build can fail, so maybe the way out is to test
> stmt_references_abnormal_ssa_name (SSA_NAME_DEF_STMT (ops[x]))
> instead of just
> SSA_NAME_OCCURS_IN_ABNORMAL_PHI (ops [x]))
> in replace_stmt_with_simplification.
Richard, does gimple-fold.c only fold the outermost expression like
fold-const.c or does it work recursively? In the former case, the above change
would be OK but, in the latter case, some changes in genmatch.c itself might be
needed.
next prev parent reply other threads:[~2015-03-23 18:36 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-23 5:21 [Bug ada/65519] New: Unable to coalesce ssa_names 2 and 87 which are marked as MUST COALESCE if ZCX_By_Default is set False syq at debian dot org
2015-03-23 5:27 ` [Bug ada/65519] " syq at debian dot org
2015-03-23 11:48 ` [Bug ada/65519] [5 regression] unable to coalesce ssa_names 2 and 87 which are marked as MUST COALESCE ebotcazou at gcc dot gnu.org
2015-03-23 11:54 ` ebotcazou at gcc dot gnu.org
2015-03-23 12:21 ` ebotcazou at gcc dot gnu.org
2015-03-23 14:27 ` ebotcazou at gcc dot gnu.org
2015-03-23 16:47 ` ebotcazou at gcc dot gnu.org
2015-03-23 19:34 ` ebotcazou at gcc dot gnu.org [this message]
2015-03-24 9:48 ` [Bug tree-optimization/65519] " rguenth at gcc dot gnu.org
2015-03-24 10:07 ` ebotcazou at gcc dot gnu.org
2015-03-24 10:10 ` ebotcazou at gcc dot gnu.org
2015-03-24 10:12 ` rguenth at gcc dot gnu.org
2015-03-24 10:13 ` ebotcazou at gcc dot gnu.org
2015-03-24 10:29 ` rguenther at suse dot de
2015-03-25 8:54 ` [Bug middle-end/65519] " rguenth at gcc dot gnu.org
2015-03-25 9:02 ` rguenth at gcc dot gnu.org
2015-03-26 10:55 ` 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=bug-65519-4-2RY8PH0ndd@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).