From: Anthony Martin <ality@pbrane.org>
To: Charles Forsyth <charles.forsyth@gmail.com>
Cc: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] C compiler error?
Date: Wed, 14 Dec 2011 18:59:45 -0800 [thread overview]
Message-ID: <20111215025945.GA16477@dinah> (raw)
In-Reply-To: <CAOw7k5hX0uCfHz4=QM8+5r119TpXaJwx9QzGAj-WgCqjywPF6A@mail.gmail.com>
Charles Forsyth <charles.forsyth@gmail.com> once said:
> that's a little tidier, but still not right. the original
> pswt.c code was fine (or nearly so). the problem is
> actually in 8c's handling of 64-bit values and registers.
I'm not sure I understand entirely. Could you
elaborate this a bit? Also I'm a bit confused
about how uvlongs are handled in 8c. Regalloc
seems to use D_F0 for signed vlongs which works
fine with the AFMOVV instructions but IIRC that
only works for signed 64-bit values. To use an
unsigned value there would have to be some sort
of pre- and post-processing before a load or
store into the FP register. I don't see code
for that anywhere. Did I miss it?
Any help is appreciated.
Thanks,
Anthony
next prev parent reply other threads:[~2011-12-15 2:59 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-13 12:42 Lucio De Re
2011-12-13 13:36 ` erik quanstrom
2011-12-13 13:52 ` Noah Evans
[not found] ` <CAJVRB2XJ2KOC1sGd+Tb3a-3ZL7Jan9OEKH+oEWWTnutQ3M-cxg@mail.gmail.c>
2011-12-13 13:55 ` erik quanstrom
2011-12-13 14:07 ` yy
2011-12-13 22:38 ` Charles Forsyth
2011-12-13 23:01 ` Russ Cox
2011-12-14 4:05 ` Lucio De Re
2011-12-14 4:08 ` Lucio De Re
2011-12-14 4:19 ` Russ Cox
2011-12-14 9:20 ` Charles Forsyth
2011-12-14 10:10 ` Anthony Martin
2011-12-14 10:29 ` Charles Forsyth
2011-12-14 10:34 ` Charles Forsyth
2011-12-15 2:59 ` Anthony Martin [this message]
2011-12-15 9:02 ` Charles Forsyth
2011-12-13 13:57 ` Anthony Martin
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=20111215025945.GA16477@dinah \
--to=ality@pbrane.org \
--cc=9fans@9fans.net \
--cc=charles.forsyth@gmail.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.
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).