From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 3DB3F3858412; Wed, 6 Jul 2022 01:00:46 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 3DB3F3858412 From: "xeioexception at gmail dot com" To: gcc-bugs@gcc.gnu.org Subject: [Bug target/106165] incorrect result when using inlined asm implementation of floor() on i686 Date: Wed, 06 Jul 2022 01:00:46 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: target X-Bugzilla-Version: 11.1.0 X-Bugzilla-Keywords: inline-asm, wrong-code X-Bugzilla-Severity: normal X-Bugzilla-Who: xeioexception at gmail dot com X-Bugzilla-Status: RESOLVED X-Bugzilla-Resolution: DUPLICATE 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 X-BeenThere: gcc-bugs@gcc.gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gcc-bugs mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 06 Jul 2022 01:00:46 -0000 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D106165 --- Comment #5 from xeioex --- My question is more practical. For example while `-fexcess-precision=3Dstan= dard` fixes the problem in GCC. But, I am left with the same problem regarding ot= her compilers. At least am looking for a way to detect excessive precision as s= oon as possible (during configure time). Tried to use FLT_EVAL_METHOD t.c ``` #include #include #include #include int main(){ printf("%d\n", (int) FLT_EVAL_METHOD); } ``` 1) gcc -o t t.c && ./t 2 2) gcc -fexcess-precision=3Dstandard -o t t.c && ./t 2 How am I expected to use FLT_EVAL_METHOD correctly?=