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 A6DD9384AB43; Thu, 11 Apr 2024 01:03:04 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org A6DD9384AB43
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1712797384;
	bh=qG90Xdb3DDjfLrZk0nGn25+jI3mNoXbirW3cvIncH4M=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=yPM7HJB+z5+aOrqHkk62XfJE0ae6RGjkOytRzl6KhT88dgzOartSCsP5ImfF05rh0
	 3UD2NSR6ZEM5KA4zhy6L+2mVIy1btrMQVmNGzegBvWIyJkJp8eqgU0nb+0Bra0vJYB
	 UwJsAMzl3xtKiN4REQNVsr7BxNtRyoJED2/I+PP4=
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/91970] arm: 64bit int to double conversion does not
 respect rounding mode
Date: Thu, 11 Apr 2024 01:03:03 +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: 10.0
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: normal
X-Bugzilla-Who: pinskia 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: 
Message-ID: <bug-91970-4-w1tC69ANno@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91970-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91970-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=3D91970

--- Comment #15 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(In reply to Thiago Jung Bauermann from comment #14)
> This came up in the context of a Linux kernel patch series providing a
> "Unified cross-architecture kernel-mode FPU API" because the AMD GPU driv=
er
> fails to build on arm with the series applied because of this issue:
>=20
> https://lore.kernel.org/linux-arm-kernel/75a37a4b-f516-40a3-b6b5-
> 4aa1636f9b60@sifive.com/

That is a totally unrelated issue from this one. The issue there is arm EABI
defines the function names rather than GCC and GCC follows the ARM EABI here
(so does clang/LLVM). so you would need to do a similar renaming for the
functions on arm (32bit).=