public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "dcb314 at hotmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/108679] New: ice in modify_call, at ipa-param-manipulation.cc:656 Date: Sun, 05 Feb 2023 16:52:12 +0000 [thread overview] Message-ID: <bug-108679-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108679 Bug ID: 108679 Summary: ice in modify_call, at ipa-param-manipulation.cc:656 Product: gcc Version: 13.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c Assignee: unassigned at gcc dot gnu.org Reporter: dcb314 at hotmail dot com Target Milestone: --- For this C code: struct S1 { signed f0; }; struct S2 { struct S1 f2; short f8; } g_18; g_732, func_6_l_17; static *func_12(); static func_6(struct S2 p_7) { func_12(func_6_l_17, p_7.f2, g_18, 0); } *func_12(int, struct S1 p_14) { safe_lshift_func_int16_t_s_u(); safe_unary_minus_func_uint64_t_u(); g_732 = safe_mul_func_uint8_t_u_u(0, p_14); } main() { struct S2 l_10 = {3}; func_6(l_10); } compiled by recent gcc, does this: $ /home/dcb36/gcc/results/bin/gcc -w -O2 -ftrivial-auto-var-init=zero bug881.c during IPA pass: inline bug881.c: In function ‘main’: bug881.c:18:3: internal compiler error: in modify_call, at ipa-param-manipulation.cc:656 18 | func_6(l_10); | ^~~~~~~~~~~~ 0xb64d40 ipa_param_adjustments::modify_call(cgraph_edge*, bool) ../../trunk.d1/gcc/ipa-param-manipulation.cc:656 The bug first seems to occur sometime between g:d0a3d55ae4a2656f and g:1530a9b1f45a7ceb
next reply other threads:[~2023-02-05 16:52 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-02-05 16:52 dcb314 at hotmail dot com [this message] 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 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@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).