From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id C26173857C4A; Thu, 7 Mar 2024 05:24:54 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org C26173857C4A DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1709789094; bh=oZFu5fb9irj1dsVrzA20KOT+BD59/7EQksFES/wNO5c=; h=From:To:Subject:Date:In-Reply-To:References:From; b=co1VUmnj9kSEsZ67ZI7oPW363EjU1pMFmPl4r3egp6MynSO0fecvdPUo0VlCG9aNc mLr4hrhqz2CCasQYd5o3me8wg6gu8F5WLlnPC03jAPcsK0bE0IjdccrB6lg3HI4kQ2 viq0xEfnxLSRu25NUwoZ2L8TsDd08xaZau3VAqKs= From: "pinskia at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug ipa/114263] LTO generating incorrect code with -O2 -std=c++20 -fno-strict-aliasing flags in GCC13 Date: Thu, 07 Mar 2024 05:24:54 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: ipa X-Bugzilla-Version: 13.2.1 X-Bugzilla-Keywords: lto, wrong-code X-Bugzilla-Severity: normal X-Bugzilla-Who: pinskia at gcc dot gnu.org X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: 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=3D114263 --- Comment #1 from Andrew Pinski --- This sounds almost the same as what is mentioned in PR 113359 ("is changed = by SRA to only store 64 + 32 bits into the std::pair rather than 64 + 64 bits.= ").=