From: Grant Grundler <grundler@parisc-linux.org>
To: John David Anglin <dave@hiauly1.hia.nrc.ca>
Cc: Kyle McMartin <kyle@mcmartin.ca>, parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] PA 2.0 float conversion to unsigned long long
Date: Mon, 18 Jul 2005 13:45:28 -0600 [thread overview]
Message-ID: <20050718194528.GD11016@colo.lackof.org> (raw)
In-Reply-To: <200507140356.j6E3uShf022345@hiauly1.hia.nrc.ca>
On Wed, Jul 13, 2005 at 11:56:28PM -0400, John David Anglin wrote:
...
> That's what I was thinking when I wrote the message. Under linux,
> both the left and right halves of fr22 end up with 0x80000000. Under
> hpux, the left result is 0x80000000 and the right 0. The only other
> explanation is that the c3k fpu has a bug that's not present in an A500
> (doubtful).
If they are running at the same clock speed, they are likely to have
identical CPUs. Some of the 440Mhz boxes did roll CPU HW version
after initial release - including some SMP bugs that C3K wouldn't
be exposed to. I'm skeptical it's a bug in the FPU unless you
can demonstrate the same code works on another (newer) CPU model.
thanks,
grant
_______________________________________________
parisc-linux mailing list
parisc-linux@lists.parisc-linux.org
http://lists.parisc-linux.org/mailman/listinfo/parisc-linux
next prev parent reply other threads:[~2005-07-18 19:45 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-14 2:53 [parisc-linux] PA 2.0 float conversion to unsigned long long John David Anglin
2005-07-14 3:32 ` Kyle McMartin
2005-07-14 3:56 ` John David Anglin
2005-07-14 6:29 ` Joel Soete
2005-07-18 19:45 ` Grant Grundler [this message]
2005-07-18 22:34 ` John David Anglin
-- strict thread matches above, loose matches on Subject: below --
2005-07-19 17:41 soete.joel
2005-07-19 18:29 ` John David Anglin
2005-07-20 15:30 soete.joel
2005-07-22 22:04 ` Joel Soete
2005-07-22 23:16 ` Kyle McMartin
2005-07-23 9:39 ` Joel Soete
2005-07-25 9:57 Joel Soete
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=20050718194528.GD11016@colo.lackof.org \
--to=grundler@parisc-linux.org \
--cc=dave@hiauly1.hia.nrc.ca \
--cc=kyle@mcmartin.ca \
--cc=parisc-linux@lists.parisc-linux.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