[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.LRH.2.02.2002231605580.21843@key0.esi.com.au>
Date: Sun, 23 Feb 2020 16:41:31 +1100 (AEDT)
From: Damian McGuckin <damianm@....com.au>
To: musl@...ts.openwall.com
Subject: Re: Considering x86-64 fenv.s to C
On Sat, 22 Feb 2020, Rich Felker wrote:
> First comment: I couldn't find (maybe I missed?) what you intend fore
> the contents of fenv-generic.c and fenv-trivial.c to be, but I don't
> see what you want them for. fenv.c should just use the macros/inlines
> the fenv_arch.h defines, naturally collapsing to empty functions when
> they do nothing (for softfloat archs).
I agree. I was seduced by what I thought was a better way.
I assume that I can also have a
fenv_arch_soft_float.h
and
fenv_arch_common_fpu.h
Each of thes is pulled in at the end of fenv_arch.h for respectively
a) those machines with a generic soft_float architecture
b) those machines with non-Intel (hard) FPUs.
Regards - Damian
Pacific Engineering Systems International, 277-279 Broadway, Glebe NSW 2037
Ph:+61-2-8571-0847 .. Fx:+61-2-9692-9623 | unsolicited email not wanted here
Views & opinions here are mine and not those of any past or present employer
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
