From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 648A83871029; Mon, 16 Mar 2020 19:28:28 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 648A83871029 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1584386908; bh=oJCnpP8jdvjI/GPtVbhTZEdQpj8Fsfo0u11HfzZDazY=; h=From:To:Subject:Date:In-Reply-To:References:From; b=fUYKdmd1YWb3L25uWZ+TEVaTD2KqcesTB33oTThSzL5rhvYl48pxpvYwrMInWDQji DbEexIpeVl3qB35uUaDHJQyTiuBOBWIM8BcU0cV5YNOBpRJnWTxEYKu73wjbZvCrC0 xPDQoGj7gz+t9aRG9I+rMuoMwIKBZWOlNLfdYU9I= From: "adhemerval.zanella at linaro dot org" To: gcc-bugs@gcc.gnu.org Subject: [Bug target/94194] x86: Provide feraiseexcept builtins Date: Mon, 16 Mar 2020 19:28:28 +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: unknown X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: adhemerval.zanella at linaro dot 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: 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: Mon, 16 Mar 2020 19:28:28 -0000 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D94194 --- Comment #2 from Adhemerval Zanella --- Afaik the libc implementation is free to set any macro value for FE_*, alth= ough glibc and other implementations I am awre of try to make is related to architecture values when it does make sense (and it also tend to simplify t= he implementation). So I would expect that the compiler either would need to export a system-neutral value (GCC_FE_* or something related) with the drawback it w= ould not be a direct replacement for the system library call (as other builtins = tend to be) or define functions that does not use input arguments (something lik= e=20 __builtin_feraiseexcept_div_by_zero). For -fno-trapping-math I would expect= to be a nop in such a scenario, although I haven't given much thought about it. However, I opened this bug more to check if this optimization would be worth implementing. My take is to remove it from glibc installed headers [1], and= my impression is this should not add much from the compiler side of view as we= ll. [1] https://sourceware.org/pipermail/libc-alpha/2020-March/111775.html=