public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jamborm at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug ipa/108679] [13 Regression] ice in modify_call, at ipa-param-manipulation.cc:656 since r13-4685-g4834e9360f7bf42f Date: Thu, 09 Feb 2023 14:22:42 +0000 [thread overview] Message-ID: <bug-108679-4-yjC97IfcD1@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-108679-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108679 --- Comment #3 from Martin Jambor <jamborm at gcc dot gnu.org> --- What happens is that ipa_param_body_adjustments::modify_call_stmt is confused by the IPA-CP produced scalar constant where it expects a structure containing just one field of the corresponding type. It is easy to avoid the situation altogether with just the following but it means that the caller (in the example func_6) will not entirely lose the parameter even though we know its contents at compile time and could re-construct it for the purposes of the call (of func_12). But the behavior is not worse than GCC 12 and before, so the patch is probably the right thing to do in stage 4. diff --git a/gcc/ipa-sra.cc b/gcc/ipa-sra.cc index 7a2b4dc8608..822fd6262d6 100644 --- a/gcc/ipa-sra.cc +++ b/gcc/ipa-sra.cc @@ -3989,7 +3989,7 @@ push_param_adjustments_for_index (isra_func_summary *ifs, unsigned base_index, { ipa_argagg_value_list avl (ipcp_ts); tree value = avl.get_value (base_index, pa->unit_offset); - if (value) + if (value && !AGGREGATE_TYPE_P (pa->type)) { if (dump_file) fprintf (dump_file, " - omitting component at byte "
next prev parent reply other threads:[~2023-02-09 14:22 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-02-05 16:52 [Bug c/108679] New: ice in modify_call, at ipa-param-manipulation.cc:656 dcb314 at hotmail dot com 2023-02-05 19:07 ` [Bug ipa/108679] [13 Regression] " pinskia at gcc dot gnu.org 2023-02-06 7:55 ` rguenth at gcc dot gnu.org 2023-02-06 9:23 ` [Bug ipa/108679] [13 Regression] ice in modify_call, at ipa-param-manipulation.cc:656 since r13-4685-g4834e9360f7bf42f marxin at gcc dot gnu.org 2023-02-09 13:13 ` jamborm at gcc dot gnu.org 2023-02-09 14:22 ` jamborm at gcc dot gnu.org [this message] 2023-02-14 14:51 ` jamborm at gcc dot gnu.org 2023-02-15 10:38 ` cvs-commit at gcc dot gnu.org 2023-02-15 10:40 ` jamborm 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-108679-4-yjC97IfcD1@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: linkBe 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).