From: Jonathan Wakely <jwakely.gcc@gmail.com>
To: Manfred Schwarb <manfred99@gmx.ch>
Cc: gcc-help <gcc-help@gcc.gnu.org>
Subject: Re: Debugging ICE in GCC
Date: Sun, 31 May 2020 21:30:13 +0100 [thread overview]
Message-ID: <CAH6eHdR7mTVZZNkOW_3fxjWHX3H3zBxz56Z1CztcEnR4L99rNw@mail.gmail.com> (raw)
In-Reply-To: <4c4e0c44-922d-df87-3d65-6a8b1d38b446@gmx.ch>
On Sun, 31 May 2020 at 14:45, Manfred Schwarb <manfred99@gmx.ch> wrote:
>
> Am 31.05.20 um 01:46 schrieb Manfred Schwarb:
> > Am 30.05.20 um 09:39 schrieb Jonathan Wakely:
> >> On Sat, 30 May 2020 at 02:01, Manfred Schwarb <manfred99@gmx.ch> wrote:
>
> >>>
> >>> I built GCC with
> >>> #> ../configure --enable-checking=yes,extra i686-linux
> >>> #> make BOOT_CFLAGS="-O2 -ggdb" bootstrap2-lean
> >>>
>
> OK, I found it. I was perhaps a bit too clever: while "bootstrap2"
> really speeds up things a lot, it seems to hamper debugability.
> So if I bootstrap with "bootstrap", my backtraces show up as they should.
You can just do "make" and not ask for any bootstrap targets. The
default is a normal bootstrap, which would have worked fine.
> BTW: is bootstrapping with BOOT_CFLAGS="-Og -g" meant to work?
Yes.
> With "-Og" I get multiple errors of the category "-Werror=maybe-uninitialized"
> and "-Werror=format-whatever" and bootstrap fails.
--disable-werror
prev parent reply other threads:[~2020-05-31 20:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-29 23:55 Manfred Schwarb
2020-05-30 2:01 ` Dan Kegel
[not found] ` <77248fa9-0729-28a1-ea61-1ed2005f9b66@gmx.ch>
2020-05-30 23:48 ` Manfred Schwarb
2020-05-30 7:39 ` Jonathan Wakely
2020-05-30 23:46 ` Manfred Schwarb
2020-05-31 13:45 ` Manfred Schwarb
2020-05-31 20:30 ` Jonathan Wakely [this message]
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=CAH6eHdR7mTVZZNkOW_3fxjWHX3H3zBxz56Z1CztcEnR4L99rNw@mail.gmail.com \
--to=jwakely.gcc@gmail.com \
--cc=gcc-help@gcc.gnu.org \
--cc=manfred99@gmx.ch \
/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).