public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: John Scott <jscott@posteo.net>
To: gcc-help@gcc.gnu.org
Subject: Help with bisecting a test suite regression in GCC
Date: Sat, 26 Mar 2022 22:41:29 +0000	[thread overview]
Message-ID: <11cb0554516ea651ca9d668d5748786ab675acef.camel@posteo.net> (raw)

[-- Attachment #1: Type: text/plain, Size: 752 bytes --]

Hi,

While working on upgrading the gcc-sh-elf Debian package from gcc 11 to
gcc 12, I think I've found a regression. I'm able to reproduce it with
an upstream bare-metal build.

I've had a hard time figuring out how to bisect it. A naive run with
git bisect start
git bisect new .
git bisect old releases/gcc-11.2.0

fails with
The merge base 250f234988b6231669a720c52101d3686d645072 is new.
The property has changed between 250f234988b6231669a720c52101d3686d645072 and [7ca388565af176bd4efd4f8db1e5e9e11e98ef45].
error: bisect run failed: 'git bisect--helper --bisect-state (null)' exited with error code -3

I'm not enough of a Git or GCC wizard to get further. Does anyone have
any advice so I can make an informative bug report?

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 252 bytes --]

             reply	other threads:[~2022-03-26 22:41 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-26 22:41 John Scott [this message]
2022-03-27  4:53 ` Jeff Law
2022-03-27  7:41 ` Jonathan Wakely

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=11cb0554516ea651ca9d668d5748786ab675acef.camel@posteo.net \
    --to=jscott@posteo.net \
    --cc=gcc-help@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).