public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "iains at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/100373] New: [12 Regression] Darwin, Compare-debug fail after r12-248-gb58dc0b803057
Date: Sat, 01 May 2021 12:47:43 +0000 [thread overview]
Message-ID: <bug-100373-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100373
Bug ID: 100373
Summary: [12 Regression] Darwin, Compare-debug fail after
r12-248-gb58dc0b803057
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: bootstrap
Assignee: unassigned at gcc dot gnu.org
Reporter: iains at gcc dot gnu.org
Target Milestone: ---
Created attachment 50725
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=50725&action=edit
tarball with asm, objects and obj dumps.
Exactly which cases fail seems to depend on the CPU in use and the OS version.
For modern CPUs (xeon w, core i5 Skylake) the fail seems to be quite reliably
in mpfr (which I build in tree). For older corei7 machines on Darwin16, I've
seen also gcc/gcc.o as mismatched.
I did a run with -save-temps -dp (asm attached).
this is on x86_64-darwin20, but the problem is seen on x86_64-darwin* AFAICT.
Backing out r12-248-gb58dc0b803057 allows bootstrap to succeed.
attached:
stage2-mpfr/src/gmp_op.o.stripped
stage2-mpfr/src/gmp_op.o
stage2-mpfr/src/gmp_op.s
s2.txt == objdump -d -r stage2-mpfr/src/gmp_op.o.stripped >s2.txt
stage3-mpfr/src/gmp_op.o.stripped
stage3-mpfr/src/gmp_op.o
stage3-mpfr/src/gmp_op.s
s3.txt == objdump -d -r stage3-mpfr/src/gmp_op.o.stripped >s3.txt
next reply other threads:[~2021-05-01 12:47 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-01 12:47 iains at gcc dot gnu.org [this message]
2021-05-01 12:49 ` [Bug bootstrap/100373] " iains at gcc dot gnu.org
2021-05-02 15:09 ` iains at gcc dot gnu.org
2021-05-03 8:00 ` rguenth at gcc dot gnu.org
2021-05-04 10:44 ` rguenth at gcc dot gnu.org
2021-05-04 10:52 ` iains at gcc dot gnu.org
2021-05-04 10:55 ` iains at gcc dot gnu.org
2021-05-04 11:03 ` rguenther at suse dot de
2021-05-04 23:45 ` iains at gcc dot gnu.org
2021-05-04 23:48 ` iains at gcc dot gnu.org
2021-05-05 8:08 ` rguenth at gcc dot gnu.org
2021-05-05 8:48 ` rguenth at gcc dot gnu.org
2021-05-05 10:20 ` iains at gcc dot gnu.org
2021-05-05 11:58 ` rguenth at gcc dot gnu.org
2021-05-05 23:44 ` iains at gcc dot gnu.org
2021-05-06 8:08 ` cvs-commit at gcc dot gnu.org
2021-05-06 8:09 ` rguenth at gcc dot gnu.org
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=bug-100373-4@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@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).