public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ro at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug d/109231] [13/14 regression] Comparison failure in libphobos/libdruntime/rt/util/typeinfo.o
Date: Wed, 14 Jun 2023 12:29:06 +0000 [thread overview]
Message-ID: <bug-109231-4-6caFscz678@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
Rainer Orth <ro at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution|--- |WORKSFORME
--- Comment #39 from Rainer Orth <ro at gcc dot gnu.org> ---
(In reply to Jakub Jelinek from comment #38)
> As nobody but Rainer managed to reproduce this and we don't know what's
> going on, postponing for 13.2.
When building the gcc-13 branch for the first time, I forgot to include the
workaround patch for this PR, still the build went just fine without. Later
on, I disabled the workaround for trunk, too, without ill effect. I guess
we can close this for now: should the issue ever reappear, I'll reopen.
prev parent reply other threads:[~2023-06-14 12:29 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-21 12:42 [Bug d/109231] New: [13 " 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
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 [this message]
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-6caFscz678@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).