From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 0149F3858C27; Wed, 14 Jun 2023 12:29:07 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 0149F3858C27 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1686745748; bh=7IvtbiuOb6gyWqwuHMEbOS+swr/JO2k+6WHOEJ7HyE8=; h=From:To:Subject:Date:In-Reply-To:References:From; b=Sa0OpONNGe2dEDehv3p1pavxythH8fnKe73lkYPu/yHRfXp+HldFo9xsyFinM0ery gpQ/ePlfWorO8YNWXTI+oW47zUlNcSib9DvH1YYvZSLxNpmtuKyhbSKicQtHJstl2Y 4roOsntE4u357vY3q6YPaOvYC0iEAlLxEFCqvkdI= From: "ro at gcc dot 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 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: d X-Bugzilla-Version: 13.0 X-Bugzilla-Keywords: build X-Bugzilla-Severity: normal X-Bugzilla-Who: ro at gcc dot gnu.org X-Bugzilla-Status: RESOLVED X-Bugzilla-Resolution: WORKSFORME X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: ibuclaw at gdcproject dot org X-Bugzilla-Target-Milestone: 13.2 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_status resolution Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 List-Id: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D109231 Rainer Orth changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution|--- |WORKSFORME --- Comment #39 from Rainer Orth --- (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.=