From: Timothy Miller <miller@techsource.com>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: klibc list <klibc@zytor.com>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: long long on 32-bit machines
Date: Wed, 28 Jan 2004 14:12:50 -0500 [thread overview]
Message-ID: <401809B2.70907@techsource.com> (raw)
In-Reply-To: <4017F991.2090604@zytor.com>
H. Peter Anvin wrote:
> Hi all,
>
> 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?
>
> I'd like to switch klibc to use the 64-bit file ABI thoughout, but it's
> a considerable porting effort, and I'm trying to figure out how to best
> manage it.
>
I don't know how it is for GCC, but when using the Sun compiler, "long
long" for 32-bit is low-high, while "long long" (or just long) for
64-bit is high-low. This has been an annoyance to me. :)
next prev parent reply other threads:[~2004-01-28 19:09 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-28 18:04 long long on 32-bit machines H. Peter Anvin
2004-01-28 19:12 ` Timothy Miller [this message]
2004-01-28 19:15 ` David S. Miller
2004-01-29 11:02 ` Paul Mackerras
2004-01-31 6:08 ` H. Peter Anvin
2004-01-31 12:23 ` [klibc] " Arnd Bergmann
2004-01-31 19:41 ` H. Peter Anvin
2004-02-01 0:41 ` Paul Mackerras
-- strict thread matches above, loose matches on Subject: below --
2004-01-28 19:22 Arnd Bergmann
2004-01-28 20:25 ` Daniel Jacobowitz
2004-01-28 20:51 Ulrich Weigand
2004-01-29 1:34 ` H. Peter Anvin
2004-01-29 9:19 ` Arnd Bergmann
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=401809B2.70907@techsource.com \
--to=miller@techsource.com \
--cc=hpa@zytor.com \
--cc=klibc@zytor.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.