public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "hubicka at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/97857] New: profiledbootstrap broken freeing speculative call summary
Date: Mon, 16 Nov 2020 18:22:26 +0000	[thread overview]
Message-ID: <bug-97857-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 97857
           Summary: profiledbootstrap broken freeing speculative call
                    summary
           Product: gcc
           Version: unknown
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: bootstrap
          Assignee: unassigned at gcc dot gnu.org
          Reporter: hubicka at gcc dot gnu.org
  Target Milestone: ---

Configuring with 
../configure --with-build-config=bootstrap-lto --enable-checking=release
--disable-plugin

leads to ICE building stage feedback libstdc++. This is already with optimized
cc1plus so it may a miscompile of cc1plus.

0x8fcd5a crash_signal
        ../../gcc/toplev.c:330
0x7ffff789c83f ???
       
/build/glibc-vjB4T1/glibc-2.28/signal/../sysdeps/unix/sysv/linux/x86_64/sigaction.c:0
0x11fcf44 vec<speculative_call_target, va_heap, vl_ptr>::release()
        ../../gcc/vec.h:1813
0x11fcf2e auto_vec<speculative_call_target, 0ul>::~auto_vec()
        ../../gcc/vec.h:1542
0x11fcf2e speculative_call_summary::~speculative_call_summary()
        ../../gcc/ipa-profile.c:178
0x11fcf2e
object_allocator<speculative_call_summary>::remove(speculative_call_summary*)
        ../../gcc/alloc-pool.h:522
0x11fcf2e
call_summary_base<speculative_call_summary>::release(speculative_call_summary*)
        ../../gcc/symbol-summary.h:625
0xd03fbe call_summary<speculative_call_summary*>::~call_summary()
        ../../gcc/symbol-summary.h:771
0x11e106f ipa_profile_call_summaries::~ipa_profile_call_summaries()
        ../../gcc/ipa-profile.c:192
0x11e106f ipa_profile_call_summaries::~ipa_profile_call_summaries()
        ../../gcc/ipa-profile.c:192
0x11e0cff ipa_profile
        ../../gcc/ipa-profile.c:1031
0x11e0cff execute
        ../../gcc/ipa-profile.c:1070

             reply	other threads:[~2020-11-16 18:22 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-16 18:22 hubicka at gcc dot gnu.org [this message]
2020-11-16 19:38 ` [Bug bootstrap/97857] [11 Regression] profiledbootstrap broken freeing speculative call summary since r11-4987-g602c6cfc79ce4ae61e277107e0a60079c1a93a97 marxin at gcc dot gnu.org
2020-11-16 19:48   ` Jan Hubicka
2020-11-16 19:48 ` hubicka at ucw dot cz
2020-11-16 19:50 ` marxin at gcc dot gnu.org
2020-11-16 19:54   ` Jan Hubicka
2020-11-16 19:54 ` hubicka at ucw dot cz
2020-11-16 19:58 ` marxin at gcc dot gnu.org
2020-11-16 20:03 ` marxin at gcc dot gnu.org
2020-11-16 20:09   ` Jan Hubicka
2020-11-16 20:09 ` hubicka at ucw dot cz
2020-11-16 21:27 ` hubicka at gcc dot gnu.org
2020-11-16 21:43   ` Jan Hubicka
2020-11-16 21:43 ` hubicka at ucw dot cz
2020-11-16 22:55 ` hubicka at ucw dot cz
2020-11-16 23:30   ` Jan Hubicka
2020-11-16 23:30 ` hubicka at ucw dot cz
2020-11-17  7:09 ` marxin at gcc dot gnu.org
2020-11-17 14:38 ` cvs-commit at gcc dot gnu.org
2020-11-17 14:43 ` hubicka 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-97857-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).