From: Jan Hubicka <hubicka@ucw.cz>
To: Jakub Jelinek <jakub@redhat.com>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>, Martin Jambor <mjambor@suse.cz>
Subject: Re: Patch ping Re: [PATCH] ipa: Avoid another ICE when dealing with type-incompatibilities (PR 108959)
Date: Tue, 4 Apr 2023 13:36:31 +0200 [thread overview]
Message-ID: <ZCwLv8QWbqZ0bi1r@kam.mff.cuni.cz> (raw)
In-Reply-To: <ZCv83ClR5iX6RjIG@tucnak>
> On Thu, Mar 23, 2023 at 11:09:19AM +0100, Martin Jambor wrote:
> > Hi,
> >
> > PR 108959 shows one more example where undefined code with type
> > incompatible accesses to stuff passed in parameters can cause an ICE
> > because we try to create a VIEW_CONVERT_EXPR of mismatching sizes:
> >
> > 1. IPA-CP tries to push one type from above,
> >
> > 2. IPA-SRA (correctly) decides the parameter is useless because it is
> > only used to construct an argument to another function which does not
> > use it and so the formal parameter should be removed,
> >
> > 3. but the code reconciling IPA-CP and IPA-SRA transformations still
> > wants to perform the IPA-CP and overrides the built-in DCE of
> > useless statements and tries to stuff constants into them
> > instead, constants of a type with mismatching type and size.
> >
> > This patch avoids the situation in IPA-SRA by purging the IPA-CP
> > results from any "aggregate" constants that are passed in parameters
> > which are detected to be useless. It also removes IPA value range and
> > bits information associated with removed parameters stored in the same
> > structure so that the useless information is not streamed later on.
> >
> > Bootstrapped and LTO-bootstrapped and tested on x86_64-linux. OK for
> > trunk?
> >
> > gcc/ChangeLog:
> >
> > 2023-03-22 Martin Jambor <mjambor@suse.cz>
> >
> > PR ipa/108959
> > * ipa-sra.cc (zap_useless_ipcp_results): New function.
> > (process_isra_node_results): Call it.
> >
> > gcc/testsuite/ChangeLog:
> >
> > 2023-03-17 Martin Jambor <mjambor@suse.cz>
> >
> > PR ipa/108959
> > * gcc.dg/ipa/pr108959.c: New test.
OK,
thanks!
Honza
prev parent reply other threads:[~2023-04-04 11:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-23 10:09 Martin Jambor
2023-04-04 10:33 ` Patch ping " Jakub Jelinek
2023-04-04 11:36 ` Jan Hubicka [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=ZCwLv8QWbqZ0bi1r@kam.mff.cuni.cz \
--to=hubicka@ucw.cz \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@redhat.com \
--cc=mjambor@suse.cz \
/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).