From: Jonathan Wakely <jwakely.gcc@gmail.com>
To: "Søren Holm" <sgh@sgh.dk>
Cc: "gcc@gcc.gnu.org" <gcc@gcc.gnu.org>
Subject: Re: Bisecting
Date: Sun, 30 Jan 2022 01:09:46 +0000 [thread overview]
Message-ID: <CAH6eHdTYtwjaxoip-w00nYBpOTp0fo6=Cfc4shJiD553tn1Zcg@mail.gmail.com> (raw)
In-Reply-To: <30d4a81d-5974-2551-185e-cb18acb4f2b8@sgh.dk>
On Sat, 29 Jan 2022, 20:25 Søren Holm via Gcc, <gcc@gcc.gnu.org> wrote:
> 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.
>
https://gcc.gnu.org/wiki/InstallingGCC is not a huge script, it's a very
small number of commands.
You can use git bisect to simplify things, but if you don't have a small
reproducer for the problem then I don't see how you can avoid doing a full
build and install. With a simple reproducer, you can just great using the
cc1 or cc1plus binary in the build tree, without installing anything.
>
> Thanks
>
> Søren Holm
>
>
next prev parent reply other threads:[~2022-01-30 1:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-29 20:24 Bisecting Søren Holm
2022-01-30 1:09 ` Jonathan Wakely [this message]
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='CAH6eHdTYtwjaxoip-w00nYBpOTp0fo6=Cfc4shJiD553tn1Zcg@mail.gmail.com' \
--to=jwakely.gcc@gmail.com \
--cc=gcc@gcc.gnu.org \
--cc=sgh@sgh.dk \
/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).