public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "doko at debian dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/98045] New: [11 Regression] ICE in compute_fn_summary, at ipa-fnsummary.c:3138 on powerpc64le-linux-gnu
Date: Sat, 28 Nov 2020 18:54:43 +0000	[thread overview]
Message-ID: <bug-98045-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 98045
           Summary: [11 Regression] ICE in compute_fn_summary, at
                    ipa-fnsummary.c:3138 on powerpc64le-linux-gnu
           Product: gcc
           Version: 11.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: target
          Assignee: unassigned at gcc dot gnu.org
          Reporter: doko at debian dot org
  Target Milestone: ---

seen with trunk 20201128, building powerpc64le-linux-gnu, compiler configured
with a profiled bootstrap configured with

         --enable-default-pie
         --enable-secureplt
         --with-cpu=power8
         --enable-targets=powerpcle-linux
         --disable-multilib
         --enable-multiarch
         --disable-werror
         --with-long-double-128
        
--enable-offload-targets=nvptx-none=/<<PKGBUILDDIR>>/debian/tmp-nvptx/usr
         --without-cuda-driver
         --enable-checking=yes,extra,rtl


during IPA pass: icf
../../src/gcc/range-op.cc:3734:1: internal compiler error: in
compute_fn_summary, at ipa-fnsummary.c:3138
 3734 | } // namespace selftest
      | ^
0x10b335cf compute_fn_summary(cgraph_node*, bool)
        ../../src/gcc/ipa-fnsummary.c:3138
0x10b9fa2b ipa_merge_profiles(cgraph_node*, cgraph_node*, bool)
        ../../src/gcc/ipa-utils.c:750
0x11d9ca63 ipa_icf::sem_function::merge(ipa_icf::sem_item*)
        ../../src/gcc/ipa-icf.c:1272
0x11da36bf ipa_icf::sem_item_optimizer::merge_classes(unsigned int, unsigned
int)
        ../../src/gcc/ipa-icf.c:3420
0x11daf377 ipa_icf::sem_item_optimizer::execute()
        ../../src/gcc/ipa-icf.c:2460
0x11db397f ipa_icf_driver
        ../../src/gcc/ipa-icf.c:3584
0x11db397f ipa_icf::pass_ipa_icf::execute(function*)
        ../../src/gcc/ipa-icf.c:3631
Please submit a full bug report,
with preprocessed source if appropriate.

[...]

make[5]: Leaving directory '/<<PKGBUILDDIR>>/build/gcc'
make[4]: *** [Makefile:5022: all-stagefeedback-gcc] Error 2
make[4]: Leaving directory '/<<PKGBUILDDIR>>/build'
make[3]: *** [Makefile:26981: stagefeedback-bubble] Error 2
make[3]: Leaving directory '/<<PKGBUILDDIR>>/build'
make[2]: *** [Makefile:27012: profiledbootstrap-lean] Error 2
make[2]: Leaving directory '/<<PKGBUILDDIR>>/build'
make[1]: *** [debian/rules2:1246: stamps/05-build-stamp] Error 2

             reply	other threads:[~2020-11-28 18:54 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-28 18:54 doko at debian dot org [this message]
2020-11-29 12:23 ` [Bug target/98045] " doko at debian dot org
2020-11-29 12:27 ` doko at debian dot org
2020-11-29 12:35 ` doko at debian dot org
2020-11-30  8:08 ` rguenth at gcc dot gnu.org
2020-11-30  8:19 ` marxin at gcc dot gnu.org
2020-11-30 10:17 ` marxin at gcc dot gnu.org
2020-12-17  9:03 ` marxin 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-98045-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: 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).