From: "Joel Soete" <soete.joel@tiscali.be>
To: "John David Anglin" <dave@hiauly1.hia.nrc.ca>, tausq@debian.org
Cc: grundler@parisc-linux.org, willy@debian.org,
parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] fdisk problems 2.4 <-> 2.6
Date: Mon, 10 Nov 2003 10:16:50 +0100 [thread overview]
Message-ID: <3F969FFE00009CDD@ocpmta2.freegates.net> (raw)
In-Reply-To: <200311100525.hAA5Pg2V002251@hiauly1.hia.nrc.ca>
>-- Original Message --
>To: tausq@debian.org
>From: "John David Anglin" <dave@hiauly1.hia.nrc.ca>
>Cc: grundler@parisc-linux.org, soete.joel@tiscali.be,
> willy@debian.org, parisc-linux@lists.parisc-linux.org
>Date: Mon, 10 Nov 2003 00:25:42 -0500 (EST)
>Subject: Re: [parisc-linux] fdisk problems 2.4 <-> 2.6
>
>
>> %R2 is not *wrong* -- it points to the right side of argument register
> 2 (jda explained this in an earlier thread), but I am not 100% sure
> %R2 will do the right thing for a 32-bit build though -- if you are
> running on a pa1.1 machine and
>he register is only 32-bit, does %R2
> automatically do the right thing with 64-bit arguments? I guess it's
> easy enough to tell by looking at the code gcc generates...
'R' simply adds 1 to the register number specified for operand 2.
This is
>the right thing to do for a DImode value running 32-bit code.
In the code that gcc generates, we use a specific set of register
pairs for long doubles (see HARD_REGNO_MODE_OK). The main question
that I would have is is the register created in the a
>m consistent
with the register allocation needed for a DImode value. I think it
would be if the mode/type for the input/output was specified
correctly. This can be done with a cast in the asm.
Dave
--
J. David Anglin
> dave.anglin@nrc-cnrc.gc.ca
National Research Council of Canada (613) 990-0752 (FAX: 952-6602)
_______________________________________________
parisc-linux mailing list
parisc-linux@lists.parisc-linux.org
http://lists.parisc-li
>ux.org/mailman/listinfo/parisc-linux
-------------------------------------------------------------------------
Tiscali ADSL: 3 mois GRATUITS! L'Internet rapide, c'est pour tout le monde.
http://reg.tiscali.be/default.asp?lg=fr
next prev parent reply other threads:[~2003-11-10 9:16 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-05 20:21 [parisc-linux] fdisk problems 2.4 <-> 2.6 Ruediger Scholz
2003-11-06 22:29 ` Matthew Wilcox
2003-11-07 17:52 ` Joel Soete
2003-11-08 1:59 ` Grant Grundler
2003-11-08 10:59 ` Joel Soete
2003-11-08 19:48 ` Grant Grundler
2003-11-08 22:15 ` Joel Soete
2003-11-09 13:50 ` Joel Soete
2003-11-09 17:57 ` Matthew Wilcox
2003-11-09 18:59 ` Joel Soete
2003-11-10 4:45 ` Grant Grundler
2003-11-10 4:55 ` Grant Grundler
2003-11-10 5:01 ` John David Anglin
2003-11-10 5:07 ` Randolph Chung
2003-11-10 5:25 ` John David Anglin
2003-11-10 9:16 ` Joel Soete [this message]
2003-11-10 9:47 ` Joel Soete
2003-11-10 18:35 ` Joel Soete
2003-11-11 11:21 ` Joel Soete
2003-11-10 9:51 ` Joel Soete
2003-11-10 16:58 ` Grant Grundler
2003-11-07 20:32 ` Ruediger Scholz
2003-11-10 21:58 ` Ruediger Scholz
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=3F969FFE00009CDD@ocpmta2.freegates.net \
--to=soete.joel@tiscali.be \
--cc=dave@hiauly1.hia.nrc.ca \
--cc=grundler@parisc-linux.org \
--cc=parisc-linux@lists.parisc-linux.org \
--cc=tausq@debian.org \
--cc=willy@debian.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