From: Jeff Law <law@redhat.com>
To: Jakub Jelinek <jakub@redhat.com>,
"Joseph S. Myers" <joseph@codesourcery.com>,
Marek Polacek <polacek@redhat.com>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] c: Fix ICE with cast to VLA [93576]
Date: Thu, 13 Feb 2020 19:35:00 -0000 [thread overview]
Message-ID: <65ae3bcb12db4ce778675ea3f24e8f2a865b68f9.camel@redhat.com> (raw)
In-Reply-To: <20200213175708.GJ17695@tucnak>
On Thu, 2020-02-13 at 18:57 +0100, Jakub Jelinek wrote:
> Hi!
>
> The following testcase ICEs, because the PR84305 changes try to evaluate
> the size earlier. If size has side-effects, that is desirable, and the
> side-effects will actually be wrapped in a SAVE_EXPR. The problem on this
> testcase is that there are no side-effects, and c_fully_fold doesn't fold
> those COMPOUND_EXPRs to constant, and while before gimplification we unshare
> trees found in the expressions, the unsharing doesn't involve TYPE_SIZE etc.
> of used types. Gimplification is destructive though, so when we gimplify
> the two nested COMPOUND_EXPRs and then try to gimplify it the second time
> for the TYPE_SIZEs, we ICE.
> Now, we could use unshare_expr in what we push to *expr, SAVE_EXPRs and
> their operands in there aren't unshared, but I really don't see a point of
> evaluating expressions that don't have side-effects before, so instead
> this just pushes there expressions that do have side-effects.
>
> Bootstrapped/regtested on x86_64-linux and i686-linux, ok for trunk and
> release branches?
>
> 2020-02-13 Jakub Jelinek <jakub@redhat.com>
>
> PR c/93576
> * c-decl.c (grokdeclarator): If this_size_varies, only push size into
> *expr if it has side effects.
>
> * gcc.dg/pr93576.c: New test.
OK
jeff
>
prev parent reply other threads:[~2020-02-13 19:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-13 17:57 Jakub Jelinek
2020-02-13 19:35 ` Jeff Law [this message]
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=65ae3bcb12db4ce778675ea3f24e8f2a865b68f9.camel@redhat.com \
--to=law@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@redhat.com \
--cc=joseph@codesourcery.com \
--cc=polacek@redhat.com \
/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).