From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id EE8673858C55; Fri, 2 Sep 2022 07:52:41 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org EE8673858C55 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1662105161; bh=Ww5zO3GCzKSHQfThzyDNU3kn2nuDipZ36dzgxU+d/fc=; h=From:To:Subject:Date:In-Reply-To:References:From; b=QAv4v2jFatEmYfPz/btoYpqUtEbkqFElwCR4QPIiG0p5Odtj6dbAFSXB/uUJd+kMQ ompDNRD8Rh9PvX7mKYRGlk9+R0z7Gk5N1kTbisMfFNgp9R/boqsStF6mXL1sUmZMml qkoe+rMoqNy/Y/1As1YDGKzdnXS42NsByEy+Zm5Y= From: "jasonwucj at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug c/100854] TS 18661-3 and backwards-incompatible setting of __FLT_EVAL_METHOD__ Date: Fri, 02 Sep 2022 07:52:40 +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: 12.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: jasonwucj at gcc dot gnu.org X-Bugzilla-Status: NEW 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: cc 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=3D100854 Chung-Ju Wu changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |andrea.corallo at arm dot = com, | |kito at gcc dot gnu.org --- Comment #5 from Chung-Ju Wu --- (In reply to Francois-Xavier Coudert from comment #2) > This affects x86_64-apple-darwin: > https://gcc.gnu.org/pipermail/gcc/2021-December/237959.html >=20 > The system header errors out on any value of __FLT_EVAL_METHOD__ > that is not -1, 0, 1, or 2. I guess this issue has been resolved by newlib implementation. :) Refer to the discussions on: https://sourceware.org/pipermail/newlib/2021/018471.html https://sourceware.org/pipermail/newlib/2022/019522.html The patches have been committed into newlib code base and it should be work= able now.=