public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/94179] [10 Regression] ICE in gimplify_expr, at gimplify.c:14399 since r10-7127-gcb99630f254aaec6
Date: Mon, 16 Mar 2020 07:41:49 +0000	[thread overview]
Message-ID: <bug-94179-4-Gb1nbTVROi@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-94179-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #3 from Richard Biener <rguenth at gcc dot gnu.org> ---
(In reply to Jakub Jelinek from comment #2)
> Created attachment 48036 [details]
> gcc10-pr94179.patch
> 
> Untested fix.
> And/or we could limit the match.pd optimization to GIMPLE only, as at least
> the C FE doesn't seem to be prepared to handle MEM_REFs and it is unclear if
> this is the only spot that needs fixing.

Doing it GIMPLE only may need additional "fixes" when people disable
forwprop though (didn't check).  IMHO the FEs better deal with all GENERIC
if they call into middle-end routines.  But I'm not against doing this
and I don't think we need to care about people doing -fno-tree-forwprop,
it's just you brought it up ... ;)

  parent reply	other threads:[~2020-03-16  7:41 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-15 12:18 [Bug c/94179] New: " marxin at gcc dot gnu.org
2020-03-15 12:19 ` [Bug c/94179] " marxin at gcc dot gnu.org
2020-03-15 12:31 ` marxin at gcc dot gnu.org
2020-03-15 16:31 ` jakub at gcc dot gnu.org
2020-03-16  7:41 ` rguenth at gcc dot gnu.org [this message]
2020-03-16 21:59 ` cvs-commit at gcc dot gnu.org
2020-03-16 22:00 ` jakub 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-94179-4-Gb1nbTVROi@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).