From: Tamar Christina <Tamar.Christina@arm.com>
To: Feng Xue OS <fxue@os.amperecomputing.com>,
Martin Jambor <mjambor@suse.cz>, Jan Hubicka <hubicka@ucw.cz>,
"gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Cc: nd <nd@arm.com>
Subject: RE: [PATCH V2] Generalized value pass-through for self-recursive function (ipa/pr93203)
Date: Tue, 11 Feb 2020 14:31:00 -0000 [thread overview]
Message-ID: <DB6PR0802MB2245C19201F178B3F925B7BDFF180@DB6PR0802MB2245.eurprd08.prod.outlook.com> (raw)
In-Reply-To: <BYAPR01MB48692D01F9AA2D191F39DFEFF7180@BYAPR01MB4869.prod.exchangelabs.com>
Hi Feng,
It looks like the option that causes this to trigger is `--param ipa-cp-eval-threshold=1`
So on AArch64 I get it to trigger with -mcpu=native -Ofast -fomit-frame-pointer -flto --param ipa-cp-eval-threshold=1
Kind Regards,
Tamar
> -----Original Message-----
> From: Feng Xue OS <fxue@os.amperecomputing.com>
> Sent: Tuesday, February 11, 2020 13:11
> To: Tamar Christina <Tamar.Christina@arm.com>; Martin Jambor
> <mjambor@suse.cz>; Jan Hubicka <hubicka@ucw.cz>; gcc-
> patches@gcc.gnu.org
> Cc: nd <nd@arm.com>
> Subject: Re: [PATCH V2] Generalized value pass-through for self-recursive
> function (ipa/pr93203)
>
> Hi Tarmar,
>
> Since I could not reproduce this ICE with my local testing on Spec2017, would
> you share your config, or command line options extracted from compilation
> of perlbench?
>
> Thanks,
> Feng
>
> ________________________________________
> From: gcc-patches-owner@gcc.gnu.org <gcc-patches-owner@gcc.gnu.org>
> on behalf of Tamar Christina <Tamar.Christina@arm.com>
> Sent: Tuesday, February 11, 2020 6:05 PM
> To: Feng Xue OS; Martin Jambor; Jan Hubicka; gcc-patches@gcc.gnu.org
> Cc: nd
> Subject: RE: [PATCH V2] Generalized value pass-through for self-recursive
> function (ipa/pr93203)
>
> Hi Feng,
>
> This patch (commit a0f6a8cb414b687f22c9011a894d5e8e398c4be0) is causing
> ICEs in the GCC and perlbench benchmark in Spec2017.
>
> during IPA pass: cp
> lto1: internal compiler error: in find_more_scalar_values_for_callers_subset,
> at ipa-cp.c:4709
> 0x1698187 find_more_scalar_values_for_callers_subset
> ../.././gcc/ipa-cp.c:4709
> 0x169f7d3 decide_about_value<tree_node*>
> ../.././gcc/ipa-cp.c:5490
> 0x169fdc3 decide_whether_version_node
> ../.././gcc/ipa-cp.c:5537
> 0x169fdc3 ipcp_decision_stage
> ../.././gcc/ipa-cp.c:5718
> 0x169fdc3 ipcp_driver
> ../.././gcc/ipa-cp.c:5901
> Please submit a full bug report,
>
> Thanks,
> Tamar
>
> > -----Original Message-----
> > From: gcc-patches-owner@gcc.gnu.org <gcc-patches-owner@gcc.gnu.org>
> On
> > Behalf Of Feng Xue OS
> > Sent: Monday, February 10, 2020 03:29
> > To: Martin Jambor <mjambor@suse.cz>; Jan Hubicka <hubicka@ucw.cz>;
> > gcc-patches@gcc.gnu.org
> > Subject: Re: [PATCH V2] Generalized value pass-through for
> > self-recursive function (ipa/pr93203)
> >
> > >> - gcc_checking_assert (item->value);
> >
> > > I've been staring at this for quite a while, trying to figure out
> > > how your patch can put NULL here before I realized it was just a
> > > clean-up
> > > :-) Sending such changes independently or pointing them out in the
> > > email/ChangeLog makes review easier.
> >
> > Ok. I'll add some description on this cleanup on ChangeLog.
> >
> > >> @@ -5564,7 +5610,6 @@ decide_whether_version_node (struct
> > cgraph_node *node)
> > >> }
> > >> clone = create_specialized_node (node, known_csts,
> known_contexts,
> > >> aggvals, callers);
> > >> - info = IPA_NODE_REF (node);
> >
> > > please either drop this change or change it to:
> > >
> > > gcc_checking_assert (info == IPA_NODE_REF (node));
> >
> > > this line of code was actually necessary when adding nodes possibly
> > > invalidated addresses of all summaries - like fast_function_summary
> > > classes still do. So if we ever decide to use fast summaries we
> > > need a test to remind us that info address must be obtained again.
> > Ok. I'm not aware that, will keep the line as original.
> >
> > Thanks,
> > Feng
next prev parent reply other threads:[~2020-02-11 14:31 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-25 13:52 [PATCH] " Feng Xue OS
2020-01-25 16:17 ` [PATCH V2] " Feng Xue OS
2020-02-03 1:57 ` Ping* " Feng Xue OS
2020-02-05 17:27 ` Martin Jambor
2020-02-10 3:28 ` Feng Xue OS
2020-02-11 10:05 ` Tamar Christina
2020-02-11 13:10 ` Feng Xue OS
2020-02-11 14:31 ` Tamar Christina [this message]
2020-02-13 5:39 ` [PATCH] Fix bug in recursiveness check for function to be cloned (ipa/pr93707) Feng Xue OS
2020-02-17 8:44 ` Tamar Christina
2020-02-18 15:16 ` Ping: " Feng Xue OS
2020-02-19 16:28 ` Martin Jambor
2020-02-20 3:36 ` Feng Xue OS
2020-02-21 18:16 ` Martin Jambor
2020-02-22 3:32 ` Feng Xue OS
2020-02-24 15:41 ` Martin Jambor
2020-02-20 12:57 ` Tamar Christina
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=DB6PR0802MB2245C19201F178B3F925B7BDFF180@DB6PR0802MB2245.eurprd08.prod.outlook.com \
--to=tamar.christina@arm.com \
--cc=fxue@os.amperecomputing.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=hubicka@ucw.cz \
--cc=mjambor@suse.cz \
--cc=nd@arm.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).