From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 1BF843858CDA; Thu, 30 Mar 2023 12:23:29 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 1BF843858CDA DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1680179009; bh=njEs5wSrJPGcPu62ve4A21Ihveowv6qocfrGekj5cyA=; h=From:To:Subject:Date:In-Reply-To:References:From; b=JoXqfUUTl8g1XonawSNjqDQR6SZg32Pf9BtlvSZS5hOSX6snRN9YE8+meqoqjg7Pu 2JzYexY4dNY0P/PHsnuxOws6FocLzyOJwvVdOS9a+joJRajZXsdh/Bbcqv93igFCXV yII1MQ0p8qjWcMG2R7IITjtkv3duWTK0GNMA8+3Q= From: "xry111 at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/109344] feraiseexcept produces incorrect code when optimizations are enabled Date: Thu, 30 Mar 2023 12:23:28 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: c++ X-Bugzilla-Version: unknown X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: xry111 at gcc dot gnu.org X-Bugzilla-Status: RESOLVED X-Bugzilla-Resolution: INVALID 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=3D109344 --- Comment #5 from Xi Ruoyao --- (In reply to albin from comment #4) > Thanks for the info. If it was fixed three years ago how come it is still > seen when using gcc (trunk) on Compiler Explorer? Is Compiler Explorer us= ing > an obsolete glibc? It uses Glibc-2.31: https://godbolt.org/z/h348q7fbh=