From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] store NaN() to memory traps on 386 (387)
Date: Mon, 2 May 2016 16:23:28 -0700 [thread overview]
Message-ID: <e193798e9c0ed9fdf3e9f125af2a934e@lilly.quanstro.net> (raw)
In-Reply-To: <CAO41-mN45T3QTYkcUhbVsbsHW_njOupZE7RXPXTZscJEjp7BUg@mail.gmail.com>
On Mon May 2 12:30:03 PDT 2016, rymg19@gmail.com wrote:
> Not crash into a flaming ball of (very vague) fire?
the obvious loop with nan
for(i in `{seq nan >[2=]}){echo $i}
prints nothing, as the body is never executed.
what would you have it do?
to cinap's point, either nan -> float doesn't trap, and there is no protection
against bad fp math, or it does trap, and one has protection against producing
inadvertant nans.
by the way, the same issue exists with sse.
- erik
next prev parent reply other threads:[~2016-05-02 23:23 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-30 12:40 cinap_lenrek
2016-04-30 23:47 ` cinap_lenrek
2016-05-02 10:16 ` erik quanstrom
2016-05-02 16:36 ` cinap_lenrek
2016-05-02 16:45 ` erik quanstrom
2016-05-02 19:05 ` cinap_lenrek
2016-05-02 19:17 ` erik quanstrom
2016-05-02 19:27 ` Ryan Gonzalez
2016-05-02 23:23 ` erik quanstrom [this message]
2016-05-03 1:13 ` cinap_lenrek
2016-05-02 19:49 ` cinap_lenrek
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=e193798e9c0ed9fdf3e9f125af2a934e@lilly.quanstro.net \
--to=quanstro@quanstro.net \
--cc=9fans@9fans.net \
/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).