public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/94217] [10 Regression] ICE in ipa_find_agg_cst_for_param, at ipa-prop.c:3467 since r10-7237-g4e3d3e40726e1b68
Date: Wed, 18 Mar 2020 19:37:04 +0000	[thread overview]
Message-ID: <bug-94217-4-51z17W3fDl@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-94217-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94217

--- Comment #5 from Martin Liška <marxin at gcc dot gnu.org> ---
Created attachment 48060
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=48060&action=edit
Reduced test-case without a warning

$ gcc -O2 -flto star.ii -shared
during IPA pass: cp
lto1: internal compiler error: in ipa_find_agg_cst_for_param, at
ipa-prop.c:3467
0x66038d ipa_find_agg_cst_for_param(ipa_agg_value_set*, tree_node*, long, bool,
bool*)
        /home/marxin/Programming/gcc/gcc/ipa-prop.c:3467
0x66038d ipa_find_agg_cst_for_param(ipa_agg_value_set*, tree_node*, long, bool,
bool*)
        /home/marxin/Programming/gcc/gcc/ipa-prop.c:3440
0xae630f evaluate_conditions_for_known_args
        /home/marxin/Programming/gcc/gcc/ipa-fnsummary.c:371
0xaefdb9 estimate_ipcp_clone_size_and_time(cgraph_node*, vec<tree_node*,
va_heap, vl_ptr>, vec<ipa_polymorphic_call_context, va_heap, vl_ptr>,
vec<ipa_agg_value_set, va_heap, vl_ptr>, int*, sreal*, sreal*, int*)
        /home/marxin/Programming/gcc/gcc/ipa-fnsummary.c:3658
0x167ff18 estimate_local_effects
        /home/marxin/Programming/gcc/gcc/ipa-cp.c:3478
0x168a26f propagate_constants_topo
        /home/marxin/Programming/gcc/gcc/ipa-cp.c:3816
0x168a26f ipcp_propagate_stage
        /home/marxin/Programming/gcc/gcc/ipa-cp.c:3912
0x168a26f ipcp_driver
        /home/marxin/Programming/gcc/gcc/ipa-cp.c:5908
0x168a26f execute
        /home/marxin/Programming/gcc/gcc/ipa-cp.c:6001
Please submit a full bug report,
with preprocessed source if appropriate.
Please include the complete backtrace with any bug report.
See <https://gcc.gnu.org/bugs/> for instructions.
lto-wrapper: fatal error: gcc returned 1 exit status
compilation terminated.
/usr/bin/ld: error: lto-wrapper failed
collect2: error: ld returned 1 exit status

  parent reply	other threads:[~2020-03-18 19:37 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-18 17:45 [Bug ipa/94217] New: " marxin at gcc dot gnu.org
2020-03-18 17:45 ` [Bug ipa/94217] " marxin at gcc dot gnu.org
2020-03-18 18:30 ` xerofoify at gmail dot com
2020-03-18 18:43 ` mpolacek at gcc dot gnu.org
2020-03-18 18:51 ` xerofoify at gmail dot com
2020-03-18 19:22 ` marxin at gcc dot gnu.org
2020-03-18 19:37 ` marxin at gcc dot gnu.org [this message]
2020-03-19  6:40 ` rguenth at gcc dot gnu.org
2020-03-19  7:43 ` rguenth at gcc dot gnu.org
2020-03-19  9:20 ` cvs-commit at gcc dot gnu.org
2020-03-19  9:20 ` rguenth at gcc dot gnu.org
2020-03-20 11:56 ` tnfchris at gcc dot gnu.org
2020-03-20 12:05 ` tnfchris at gcc dot gnu.org
2020-03-20 16:21 ` tnfchris at gcc dot gnu.org
2020-03-20 16:25 ` marxin at gcc dot gnu.org
2020-03-20 17:28 ` tnfchris 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-94217-4-51z17W3fDl@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: 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).