From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <sourceware-bugzilla@sourceware.org>
Received: by sourceware.org (Postfix, from userid 48)
 id 27D96385841E; Tue,  8 Feb 2022 19:34:41 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 27D96385841E
From: "joseph at codesourcery dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug ports/28872] Building glibc for MIPSel single float targets
Date: Tue, 08 Feb 2022 19:34:40 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: glibc
X-Bugzilla-Component: ports
X-Bugzilla-Version: 2.30
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: critical
X-Bugzilla-Who: joseph at codesourcery dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at sourceware dot org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-28872-131-KRY9fvyJpw@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-28872-131@http.sourceware.org/bugzilla/>
References: <bug-28872-131@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-BeenThere: glibc-bugs@sourceware.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Glibc-bugs mailing list <glibc-bugs.sourceware.org>
List-Unsubscribe: <https://sourceware.org/mailman/options/glibc-bugs>,
 <mailto:glibc-bugs-request@sourceware.org?subject=unsubscribe>
List-Archive: <https://sourceware.org/pipermail/glibc-bugs/>
List-Help: <mailto:glibc-bugs-request@sourceware.org?subject=help>
List-Subscribe: <https://sourceware.org/mailman/listinfo/glibc-bugs>,
 <mailto:glibc-bugs-request@sourceware.org?subject=subscribe>
X-List-Received-Date: Tue, 08 Feb 2022 19:34:41 -0000

https://sourceware.org/bugzilla/show_bug.cgi?id=3D28872

--- Comment #3 from joseph at codesourcery dot com <joseph at codesourcery =
dot com> ---
On Tue, 8 Feb 2022, archicharmer at mail dot ru via Glibc-bugs wrote:

> https://sourceware.org/bugzilla/show_bug.cgi?id=3D28872
>=20
> --- Comment #2 from Den <archicharmer at mail dot ru> ---
> > As stated in the component description, please do not file new bugs in =
the=20
> > obsolete ports component.
> Sorry for that... then maybe you can direct me where to fill it?

libc is probably appropriate.

> > What ABI are you using for this port?
> > <https://sourceware.org/glibc/wiki/ABIList>.
> If to note from the list, it's
> classic NaN, o32, hard-float, LE: /lib/ld.so.1
> but the hardware, r5900 processor, supports only single float.

But are double-precision values passed in exactly the same way as when=20
building for a processor supporting double-precision in hardware, so that=20
objects built for double-precision hardware could run against a shared=20
libm built for single-precision hardware, passing double values to the=20
libm functions that take double arguments and getting double return values=
=20
from them, as long as this is run in double-precision hardware, for=20
example?  (That's how the 32-bit Arm hard-float AAPCS variant works, for=20
example - even processors with only single-precision float in hardware=20
have double-precision registers and double-precision loads and stores, so=20
there is no separate single-precision ABI.  Though such processors aren't=20
actually relevant for glibc because they aren't 'A' variant.)

--=20
You are receiving this mail because:
You are on the CC list for the bug.=