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 2A6803858C83; Mon, 27 Mar 2023 13:55:10 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 2A6803858C83
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1679925310;
	bh=09wqRz2OkE92EdNoHxQKx80pZQalzU0PUJkzWMOcSoQ=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=rv1Hfbk2rdZpIQ4rt+KZ/AqDyZ1CrHhjzFEJKwWgBvo2+ZjuEh8wDQBhM+iB4JCn/
	 MvV5Bxs+rhh/ef4UbpMqwXTqiFMvz/SbGSjogTDVzj2wLWNFIuEBb0V5Angi09aLhA
	 26vLtpHbzTft8SI/j4TUWXais8adu4ts8cSbFagE=
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/109294] Inconsistent exp function implementations for
 compile time and run time evaluation
Date: Mon, 27 Mar 2023 13:55:09 +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.2.0
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi 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: <bug-109294-4-QiPM4mlvx5@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-109294-4@http.gcc.gnu.org/bugzilla/>
References: <bug-109294-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=3D109294

--- Comment #2 from Jonathan Wakely <redi at gcc dot gnu.org> ---
(In reply to D=C3=A1vid P=C3=A9ter J=C3=A1nosa from comment #0)
> Based on the calls, the same binary will provide different results for use
> case 1 vs 3 which is a bug.
> Also, the result will be different for use case 2 in -O0 and -O3, which is
> also a bug.

No, those are not bugs, see the discussion in
https://www.open-std.org/jtc1/sc22/wg21/docs/papers/2023/p1383r1.pdf

It's not reasonable to expect the exact same results for floating-point mat=
hs
under all conditions.=