public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ro at CeBiTec dot Uni-Bielefeld.DE" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug d/109231] [13 regression] Comparison failure in libphobos/libdruntime/rt/util/typeinfo.o
Date: Wed, 29 Mar 2023 08:53:00 +0000	[thread overview]
Message-ID: <bug-109231-4-gg5r9suPyZ@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-109231-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109231

--- Comment #22 from ro at CeBiTec dot Uni-Bielefeld.DE <ro at CeBiTec dot Uni-Bielefeld.DE> ---
> --- Comment #21 from ro at CeBiTec dot Uni-Bielefeld.DE <ro at CeBiTec dot
> Uni-Bielefeld.DE> ---
>> --- Comment #20 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
>> Tried valgrind on the cross d21 on x86_64 and didn't see anything.
>> Perhaps modify the makefiles such that it uses -fdump-tree-all -da already when
>> compiling typeinfo.lo?
>
> I'll give that a whirl.  However, my SPARC box is pretty busy right now
> with the weekly bootstraps, so this will be later this weekend only.

Bootstrapping with

        GDCFLAGS_FOR_TARGET='-O2 -g -fdump-tree-optimized -da'

didn't show the comparison failure.

> In the meantime, I try to reproduce the issue on gcc211.

That didn't show the failure either.

To make things even more weird, I've run several regular bootstraps
since:

* Friday night:

** Solaris 11.4 trunk (latest development build, bare metal, SPARC-S7):
  32-bit gas/ld and 32-bit gas/gld bootstraps failed with the comparison
  failure, while 64-bit gas/ld completed.

** Solaris 11.4 (latest update, kernel zone/VM, different host,
   SPARC-T5): 32-bit gas/ld failed.

** Solaris 11.3 (latest update, kernel zone/VM, SPARC-S7): 32-bit gas/ld
   failed.

* Monday night: 32-bit gas/ld bootstrap passed.

* Tuesday night: 32-bit gas/ld bootstrap failed again.

Seems incredibly fragile, unfortunately.

  parent reply	other threads:[~2023-03-29  8:53 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-21 12:42 [Bug d/109231] New: " ro at gcc dot gnu.org
2023-03-21 12:42 ` [Bug d/109231] " ro at gcc dot gnu.org
2023-03-21 12:49 ` jakub at gcc dot gnu.org
2023-03-21 12:58 ` ro at CeBiTec dot Uni-Bielefeld.DE
2023-03-21 14:02 ` jakub at gcc dot gnu.org
2023-03-21 14:36 ` ro at CeBiTec dot Uni-Bielefeld.DE
2023-03-21 15:16 ` jakub at gcc dot gnu.org
2023-03-21 15:18 ` ro at gcc dot gnu.org
2023-03-21 15:37 ` jakub at gcc dot gnu.org
2023-03-21 16:21 ` ro at CeBiTec dot Uni-Bielefeld.DE
2023-03-22  6:51 ` ro at CeBiTec dot Uni-Bielefeld.DE
2023-03-22 13:29 ` jakub at gcc dot gnu.org
2023-03-22 14:01 ` jakub at gcc dot gnu.org
2023-03-22 16:12 ` jakub at gcc dot gnu.org
2023-03-22 16:55 ` jakub at gcc dot gnu.org
2023-03-22 17:03 ` ro at CeBiTec dot Uni-Bielefeld.DE
2023-03-22 21:31 ` jakub at gcc dot gnu.org
2023-03-23  9:16 ` jakub at gcc dot gnu.org
2023-03-23 12:18 ` ro at CeBiTec dot Uni-Bielefeld.DE
2023-03-23 12:28 ` ro at CeBiTec dot Uni-Bielefeld.DE
2023-03-23 12:32 ` ro at CeBiTec dot Uni-Bielefeld.DE
2023-03-24 12:40 ` jakub at gcc dot gnu.org
2023-03-24 13:08 ` ro at CeBiTec dot Uni-Bielefeld.DE
2023-03-29  8:53 ` ro at CeBiTec dot Uni-Bielefeld.DE [this message]
2023-03-29 10:51 ` jakub at gcc dot gnu.org
2023-03-29 15:00 ` ro at CeBiTec dot Uni-Bielefeld.DE
2023-03-29 15:08 ` jakub at gcc dot gnu.org
2023-03-29 15:11 ` ro at CeBiTec dot Uni-Bielefeld.DE
2023-03-29 15:13 ` jakub at gcc dot gnu.org
2023-03-30 13:30 ` ro at CeBiTec dot Uni-Bielefeld.DE
2023-03-30 13:44 ` jakub at gcc dot gnu.org
2023-03-30 16:22 ` jakub at gcc dot gnu.org
2023-03-30 18:17 ` jakub at gcc dot gnu.org
2023-03-31  7:57 ` ro at CeBiTec dot Uni-Bielefeld.DE
2023-03-31  7:59 ` jakub at gcc dot gnu.org
2023-03-31  9:22 ` ro at CeBiTec dot Uni-Bielefeld.DE
2023-03-31  9:26 ` jakub at gcc dot gnu.org
2023-03-31 12:15 ` ro at CeBiTec dot Uni-Bielefeld.DE
2023-03-31 12:28 ` jakub at gcc dot gnu.org
2023-04-17 15:14 ` [Bug d/109231] [13/14 " jakub at gcc dot gnu.org
2023-06-14 12:29 ` ro 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-109231-4-gg5r9suPyZ@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).