From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] fp crash
Date: Mon, 28 Jan 2013 19:08:16 -0500 [thread overview]
Message-ID: <1d8d7862b8cec2fabf4908f74cee6d7a@ladd.quanstro.net> (raw)
In-Reply-To: <CAOw7k5j=bpybdx7=qES_AVJ64vSiOUzuUpjxv9Vak6qaNPp-nw@mail.gmail.com>
On Mon Jan 28 18:51:38 EST 2013, charles.forsyth@gmail.com wrote:
> On 28 January 2013 23:37, erik quanstrom <quanstro@quanstro.net> wrote:
> > is the compiler free to assume that
> > d2 has not been modified?
>
> It's free to do it, but whether it ought to is another matter.
> Your specific example has appeared once before, but I can't remember
> the context and resolution
> (it might have turned up in Inferno).
>
> uvlong won't be stored in register(s) in your version of 5c, so it
> won't behave the same way.
what's the cannonical clean way of getting away with punning?
- erik
next prev parent reply other threads:[~2013-01-29 0:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-28 23:37 erik quanstrom
2013-01-28 23:50 ` Charles Forsyth
2013-01-29 0:08 ` erik quanstrom [this message]
2013-01-29 1:41 ` erik quanstrom
2013-01-29 3:27 ` Charles Forsyth
2013-01-29 3:34 ` erik quanstrom
2013-01-29 17:17 ` Charles Forsyth
2013-01-29 17:19 ` erik quanstrom
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=1d8d7862b8cec2fabf4908f74cee6d7a@ladd.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).