From: Szabolcs Nagy <nsz@port70.net>
To: musl@lists.openwall.com
Subject: Re: mips port working! & remaining issues
Date: Fri, 13 Jul 2012 10:15:25 +0200 [thread overview]
Message-ID: <20120713081525.GA14463@port70.net> (raw)
In-Reply-To: <20120713052313.GA20369@brightrain.aerifal.cx>
* Rich Felker <dalias@aerifal.cx> [2012-07-13 01:23:13 -0400]:
> Another major omission shared with arm is that setjmp/longjmp cannot
> preserve floating point registers. This is because I don't yet know
> how to determine at runtime whether hard-float is available, and the
> registers can't be saved unless they can be determined to exist. Help
> solving this problem would also be appreciated.
>
then use compile time check:
if libc is compiled with -msoft-float then dont save the registers
otherwise save them
i guess gcc has some predefined macro so you can check soft float
at compile time
when gcc compiles with hard float for mips there will be a
a .gnu.attributes section in the object file which is dumped
by readelf as
Tag_GNU_MIPS_ABI_FP: Hard float (-mdouble-float)
and binutils ld warns when such .o is linked with a soft-float .o
so i think we shouldn't worry about applications using hard float
while the libc is soft float
as for runtime check
on mips you may grep for '^ FPU' in /proc/cpuinfo
on arm '^Features' tells the fpu variant
but i guess these are not very robust
http://git.kernel.org/?p=linux/kernel/git/stable/linux-stable.git;a=blob;f=arch/mips/kernel/proc.c
http://git.kernel.org/?p=linux/kernel/git/stable/linux-stable.git;a=blob;f=arch/arm/kernel/setup.c
next prev parent reply other threads:[~2012-07-13 8:15 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-13 5:23 Rich Felker
2012-07-13 8:15 ` Szabolcs Nagy [this message]
2012-07-13 8:18 ` Justin Cormack
2012-07-13 13:08 ` Rich Felker
2012-07-13 13:36 ` Luca Barbato
2012-07-13 14:25 ` Rich Felker
2012-07-13 16:10 ` Szabolcs Nagy
2012-07-13 17:34 ` Rich Felker
2012-07-13 20:40 ` Szabolcs Nagy
2012-07-13 20:58 ` idunham
2012-07-13 22:18 ` Rich Felker
2012-07-13 15:15 ` Gregor Richards
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20120713081525.GA14463@port70.net \
--to=nsz@port70.net \
--cc=musl@lists.openwall.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/musl/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).