From: Martin Sebor <msebor@gmail.com>
To: gcc mailing list <gcc@gcc.gnu.org>
Subject: is re-running bootstrap after a change safe?
Date: Fri, 05 Apr 2019 19:55:00 -0000 [thread overview]
Message-ID: <52db8781-a1f8-5fe1-7e05-ba3f984d9825@gmail.com> (raw)
Is it safe to rerun make bootstrap after changing GCC source?
Say if the first bootstrap succeeds and I then change a single
GCC .c file and rerun make bootstrap, am I guaranteed to see
the same fallout of the change as I would if I did a pristine
build in a clean directory?
I have been assuming this is safe and so after each tweak to
a patch I work on I rerun make bootstrap in the same build
directory. It can speed things up quite a bit.
But the recent bootstrap breakage (PR 89980) makes me wonder
if it is, in fact, safe. I can see the broken bootstrap today
in a clean build yet the bootstrap I did just before checking
in the change went fine.
Martin
next reply other threads:[~2019-04-05 19:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-05 19:55 Martin Sebor [this message]
2019-04-05 20:01 ` H.J. Lu
2019-04-05 20:50 ` Eric Botcazou
2019-04-05 21:29 ` Jeff Law
2019-04-05 21:37 ` Martin Sebor
2019-04-05 22:02 ` Jeff Law
2019-04-05 23:08 ` Martin Sebor
2019-04-06 6:40 ` Andreas Schwab
2019-04-08 9:20 ` Richard Biener
2019-04-08 12:59 ` Jeff Law
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=52db8781-a1f8-5fe1-7e05-ba3f984d9825@gmail.com \
--to=msebor@gmail.com \
--cc=gcc@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).