public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenther at suse dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/96128] [11 Regression] ICE in do_store_flag, at expr.c:12247 since r11-1445-g502d63b6d6141597bb18fd23c87736a1b384cf8f
Date: Thu, 09 Jul 2020 12:43:49 +0000	[thread overview]
Message-ID: <bug-96128-4-IzPZmxlJdD@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-96128-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96128

--- Comment #3 from rguenther at suse dot de <rguenther at suse dot de> ---
On Thu, 9 Jul 2020, marxin at gcc dot gnu.org wrote:

> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96128
> 
> --- Comment #2 from Martin Liška <marxin at gcc dot gnu.org> ---
> (In reply to Richard Biener from comment #1)
> > Just trace make_ssa_name ...
> 
> So this one is leftover from gimplify.c where we expand the first argument to
> assignment to a SSA NAME and so we end up only with the vector comparisons, but
> no VEC_COND_EXPR.
> Would it be possible to remove the SSA_NAME in gimplify.c when we know the
> VEC_COND_EXPR is expanded to no-op?

Somehow switch gimplifying of the operand and evaluating "expanded to 
no-op", other than that, no - the gimplifier doesn't perform DCE.

  parent reply	other threads:[~2020-07-09 12:43 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-09  8:04 [Bug target/96128] New: " marxin at gcc dot gnu.org
2020-07-09  8:06 ` [Bug target/96128] " marxin at gcc dot gnu.org
2020-07-09 11:38 ` rguenth at gcc dot gnu.org
2020-07-09 12:38 ` marxin at gcc dot gnu.org
2020-07-09 12:43 ` rguenther at suse dot de [this message]
2020-07-09 12:52 ` marxin at gcc dot gnu.org
2020-07-27 13:04 ` [Bug tree-optimization/96128] " cvs-commit at gcc dot gnu.org
2020-07-27 13:04 ` marxin 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-96128-4-IzPZmxlJdD@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).