From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-bugzilla@gcc.gnu.org>
Received: by sourceware.org (Postfix, from userid 48)
	id 4791C394D8B9; Wed, 16 Nov 2022 01:41:59 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 4791C394D8B9
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1668562919;
	bh=6j8xT2rJIMZVWCwcpRn6+ftPLWPM+9gusvlopk3dkss=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=pvYy62bac7QJi9SLgF97rE08MqUNGQXvjvdsQF0jxRkRLi0bqs/Gb/dE9AG5yHyqU
	 vihWhvXCrQ6uRhB50B+NsEKNIEUuLxTDItPrKchpzsZWxEoT8k+k1cAN79vy6U8a8n
	 bSw6EcEYahzrsGqlh/skMHsFXBn7yxSjpO0t7srk=
From: "t3suzuki at ucsd dot edu" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/107660] Running binaries compiled with g++11 or later
 produces different results than g++ version 10 or earlier
Date: Wed, 16 Nov 2022 01:41:58 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 12.2.0
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: normal
X-Bugzilla-Who: t3suzuki at ucsd dot edu
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: <bug-107660-4-hqkW3tvyRU@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-107660-4@http.gcc.gnu.org/bugzilla/>
References: <bug-107660-4@http.gcc.gnu.org/bugzilla/>
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: <gcc-bugs.sourceware.org>

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

--- Comment #9 from Tomoya Suzuki <t3suzuki at ucsd dot edu> ---
Thanks for clarifying the cause. I don't think you need to add the macro ju=
st
for me, gcc11 behavior is not critical for me.=