public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "hubicka at ucw dot cz" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/97857] [11 Regression] profiledbootstrap broken freeing speculative call summary since r11-4987-g602c6cfc79ce4ae61e277107e0a60079c1a93a97
Date: Mon, 16 Nov 2020 19:48:34 +0000	[thread overview]
Message-ID: <bug-97857-4-XOF39eFn7k@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-97857-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #2 from Jan Hubicka <hubicka at ucw dot cz> ---
> I see a similar bootstrap failure that's with:
> 
> ../configure --enable-languages=c,c++,lto --prefix=/home/marxin/bin/gcc
> --disable-multilib --without-isl --disable-libsanitizer
> --with-build-config=bootstrap-lto-lean && make profiledbootstrap
> 'STAGE1_CFLAGS=-g -O2'
> 
> started with r11-4987-g602c6cfc79ce4ae61e277107e0a60079c1a93a97.

Yep, I already worked out it is ipa-icf...
Do you have easy way to bisect what merge is causing the failure?
It is odd it reproduces only with profile feedback and now without since
ICF does not care about it very much.

Honza

  parent reply	other threads:[~2020-11-16 19:48 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-16 18:22 [Bug bootstrap/97857] New: profiledbootstrap broken freeing speculative call summary hubicka at gcc dot gnu.org
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 [this message]
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-XOF39eFn7k@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).