From: "Søren Holm" <sgh@sgh.dk>
To: gcc@gcc.gnu.org
Subject: Bisecting
Date: Sat, 29 Jan 2022 21:24:46 +0100 [thread overview]
Message-ID: <30d4a81d-5974-2551-185e-cb18acb4f2b8@sgh.dk> (raw)
Hi
I believe I have found some kind of bug in GCC. The target is a
cortex-m7 CPU. I do not have an isolated test software so I'm thinking
of bisecting GCC between GCC 9.4 and 10.1.
Are there any easy way do do a fast "change - compile - test"- cycle -
and how do I do that? All the guide on building GCC is using huge
scripts with installs and such. I'm sure the main developers does not do
that.
Thanks
Søren Holm
next reply other threads:[~2022-01-29 20:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-29 20:24 Søren Holm [this message]
2022-01-30 1:09 ` Bisecting Jonathan Wakely
2022-01-30 18:59 ` Bisecting David Malcolm
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=30d4a81d-5974-2551-185e-cb18acb4f2b8@sgh.dk \
--to=sgh@sgh.dk \
--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).