public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <dan@debian.org>
To: linux-kernel@vger.kernel.org
Subject: Re: long long on 32-bit machines
Date: Wed, 28 Jan 2004 15:25:51 -0500	[thread overview]
Message-ID: <20040128202551.GA16884@nevyn.them.org> (raw)
In-Reply-To: <26879984$107531702940180925001758.71044950@config16.schlund.de>

On Wed, Jan 28, 2004 at 08:22:01PM +0100, Arnd Bergmann wrote:
> 
> H.P.A wrote:
> 
> > Does anyone happen to know if there are *any* 32-bit architectures (on 
> > which Linux runs) for which the ABI for a "long long" is different from 
> > passing two "longs" in the appropriate order, i.e. (hi,lo) for bigendian 
> > or (lo,hi) for littleendian?
> 
> Some architectures require long long arguments to be passed as an
> even/odd register pair. For example on s390, 
> 
>    void f(int a, int b, long long x) 
> 
> uses registers 2, 3, 4 and 5, while 
> 
>    void f(int a, long long x, int b)
> 
> uses registers 2, 4, 5 and 6. AFAIK, mips does the same, probably others
> as well.

Yes.  Also, IIRC, one of SH3 and SH4 requires the padding, and the
other doesn't.

-- 
Daniel Jacobowitz
MontaVista Software                         Debian GNU/Linux Developer

  reply	other threads:[~2004-01-28 20:25 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-28 19:22 long long on 32-bit machines Arnd Bergmann
2004-01-28 20:25 ` Daniel Jacobowitz [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-01-28 20:51 Ulrich Weigand
2004-01-29  1:34 ` H. Peter Anvin
2004-01-29  9:19   ` Arnd Bergmann
2004-01-28 18:04 H. Peter Anvin
2004-01-28 19:12 ` Timothy Miller
2004-01-28 19:15   ` David S. Miller
2004-01-29 11:02 ` Paul Mackerras
2004-01-31  6:08   ` H. Peter Anvin
2004-02-01  0:41     ` Paul Mackerras

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=20040128202551.GA16884@nevyn.them.org \
    --to=dan@debian.org \
    --cc=linux-kernel@vger.kernel.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