public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug bootstrap/98338] New: [11 Regression] profiledbootstrap failure on x86_64-linux Date: Thu, 17 Dec 2020 00:50:38 +0000 [thread overview] Message-ID: <bug-98338-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98338 Bug ID: 98338 Summary: [11 Regression] profiledbootstrap failure on x86_64-linux Product: gcc Version: 11.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: bootstrap Assignee: unassigned at gcc dot gnu.org Reporter: jakub at gcc dot gnu.org CC: marxin at gcc dot gnu.org Target Milestone: --- r11-6148 fails profiledbootstrap on x86_64-linux, the error is: during IPA pass: icf ../../gcc/range-op.cc:3444:1: internal compiler error: in compute_fn_summary, at ipa-fnsummary.c:3138 0x1385f82 compute_fn_summary(cgraph_node*, bool) ../../gcc/ipa-fnsummary.c:3138 0x14092d3 ipa_merge_profiles(cgraph_node*, cgraph_node*, bool) ../../gcc/ipa-utils.c:750 0x28af067 ipa_icf::sem_function::merge(ipa_icf::sem_item*) ../../gcc/ipa-icf.c:1272 0x28b7290 ipa_icf::sem_item_optimizer::merge_classes(unsigned int, unsigned int) ../../gcc/ipa-icf.c:3420 0x28b3b85 ipa_icf::sem_item_optimizer::execute() ../../gcc/ipa-icf.c:2460 0x28b7ab4 ipa_icf_driver ../../gcc/ipa-icf.c:3584 0x28ba37e ipa_icf::pass_ipa_icf::execute(function*) ../../gcc/ipa-icf.c:3631 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. Reduced testcase: .../cc1plus -fpreprocessed range-op.ii -quiet -dumpbase range-op.cc -dumpbase-ext .cc -mtune=generic -march=x86-64 -g -grecord-gcc-switches -O2 -Wformat-security -Wextra -Wall -Wno-narrowing -Wwrite-strings -Wcast-qual -Wno-error=format-diag -Wsuggest-attribute=format -Woverloaded-virtual -Wpedantic -Wno-long-long -Wno-variadic-macros -Wno-overlength-strings -version -fno-PIE -fstack-clash-protection -fcf-protection=full -fprofile-use -fno-exceptions -fno-rtti -fasynchronous-unwind-tables -o range-op.s I'll attach range-op.ii and range-op.gcda
next reply other threads:[~2020-12-17 0:50 UTC|newest] Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-12-17 0:50 jakub at gcc dot gnu.org [this message] 2020-12-17 0:52 ` [Bug bootstrap/98338] " jakub at gcc dot gnu.org 2020-12-17 0:53 ` jakub at gcc dot gnu.org 2020-12-17 8:31 ` marxin at gcc dot gnu.org 2020-12-17 9:03 ` marxin at gcc dot gnu.org 2020-12-17 9:50 ` marxin at gcc dot gnu.org 2020-12-17 9:51 ` marxin at gcc dot gnu.org 2020-12-17 10:02 ` jakub at gcc dot gnu.org 2020-12-17 10:06 ` marxin at gcc dot gnu.org 2020-12-17 10:09 ` marxin at gcc dot gnu.org 2021-01-04 15:45 ` rguenth at gcc dot gnu.org 2021-01-28 16:08 ` jakub at gcc dot gnu.org 2021-01-28 21:26 ` hubicka at ucw dot cz 2021-01-28 21:34 ` hubicka at ucw dot cz 2021-01-29 17:16 ` jakub at gcc dot gnu.org 2021-02-01 8:26 ` marxin at gcc dot gnu.org 2021-02-12 17:32 ` marxin at gcc dot gnu.org 2021-02-12 17:33 ` [Bug bootstrap/98338] [10/11 " marxin at gcc dot gnu.org 2021-02-14 22:31 ` hubicka at gcc dot gnu.org 2021-02-26 12:21 ` jakub at gcc dot gnu.org 2021-02-26 17:07 ` hubicka at ucw dot cz 2021-02-26 17:36 ` jakub at gcc dot gnu.org 2021-02-26 17:38 ` Jan Hubicka 2021-02-26 17:38 ` hubicka at ucw dot cz 2021-02-26 17:42 ` jakub at gcc dot gnu.org 2021-03-01 12:25 ` jakub at gcc dot gnu.org 2021-03-01 13:37 ` cvs-commit at gcc dot gnu.org 2021-03-01 13:38 ` hubicka at gcc dot gnu.org 2021-03-02 14:54 ` cvs-commit 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-98338-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).