From: Jonas Amoson <jonas.amoson@gmail.com>
To: 9front@9front.org
Subject: Re: [9front] bring ape/float.h macros in line with u.h
Date: Thu, 4 Feb 2021 01:06:43 +0200 [thread overview]
Message-ID: <CAF46DJ4ykoceRqZ7Nr5pFmtcwSUyOkP4yTiR5cjZBA91ObFqKQ@mail.gmail.com> (raw)
In-Reply-To: <3da4f880-0941-4dcd-b5cb-b8055103e3fb@www.fastmail.com>
This looks like the right thing to me.
I don’t see why APE would be different
here than the native u.h. Right now only
amd64 defines FPINVAL in both u.h and
APE, but all other architectures have it
defined in u.h. Phils’ latest changes to
netsurf flips FPINVAL in order for it to be
less sensitive in certain calculations (i.e.
resulting in a divide by zero). For example,
oading http://www.theregister.co.uk works
if FPINVAL is flipped, and crashes if not.
This is not my discovery, I bumped into the
same compilation error, and was informed.
Any objections for including the patch?
On Mon, 1 Feb 2021 at 21:15, james palmer <james@biobuf.link> wrote:
>
> noticed this building netsurf on 386.
> this fixes it for all architectures.
>
> - james
prev parent reply other threads:[~2021-02-05 11:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-01 18:39 james palmer
2021-02-03 23:06 ` Jonas Amoson [this message]
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=CAF46DJ4ykoceRqZ7Nr5pFmtcwSUyOkP4yTiR5cjZBA91ObFqKQ@mail.gmail.com \
--to=jonas.amoson@gmail.com \
--cc=9front@9front.org \
/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.
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).