From: Matthew Wilcox <matthew@wil.cx>
To: Kyle Moffett <mrmacman_g4@mac.com>
Cc: Adrian Bunk <bunk@stusta.de>,
LKML Kernel <linux-kernel@vger.kernel.org>,
David Woodhouse <dwmw2@infradead.org>,
david@lang.hm, linux-arch@vger.kernel.org
Subject: Re: Userspace compiler support of "long long"
Date: Wed, 27 Jun 2007 21:57:54 -0600 [thread overview]
Message-ID: <20070628035754.GB22063@parisc-linux.org> (raw)
In-Reply-To: <B3C8EEBF-71FB-4169-8ED7-7C4A410BBEE1@mac.com>
On Wed, Jun 27, 2007 at 06:30:52PM -0400, Kyle Moffett wrote:
> Then all 64-bit archs have:
> typedef signed long __s64;
> typedef unsigned long __u64;
>
> While all 32-bit archs have:
> typedef signed long long __s64;
> typedef unsigned long long __u64;
include/asm-parisc/types.h:typedef unsigned long long __u64;
For both 32 and 64-bit.
include/asm-sh64/types.h:typedef unsigned long long __u64;
include/asm-x86_64/types.h:typedef unsigned long long __u64;
So that's three architectures that violate your first assertion.
next prev parent reply other threads:[~2007-06-28 3:57 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <467afc63.OnsqEXOk5zqMYzym%Joerg.Schilling@fokus.fraunhofer.de>
[not found] ` <Pine.LNX.4.64.0706211620080.31603@asgard.lang.hm>
[not found] ` <467b0bf2.Xfs7T8Ys4nY9ZNLW%Joerg.Schilling@fokus.fraunhofer.de>
[not found] ` <1182483527.10524.31.camel@shinybook.infradead.org>
[not found] ` <20070622150038.GN23017@stusta.de>
[not found] ` <E27BAC4D-2F1E-4191-A75D-4DD18231C320@mac.com>
[not found] ` <20070627154046.GN1094@stusta.de>
[not found] ` <468287a8.spBb6PdAZ4QV0j2Y%Joerg.Schilling@fokus.fraunhofer.de>
[not found] ` <20070627173240.GR1094@stusta.de>
2007-06-27 22:30 ` Userspace compiler support of "long long" Kyle Moffett
2007-06-27 22:57 ` Randy Dunlap
2007-06-27 23:16 ` Randy Dunlap
2007-06-28 2:12 ` Geert Uytterhoeven
2007-06-28 6:50 ` Jan Engelhardt
2007-06-28 11:34 ` Geert Uytterhoeven
2007-06-28 11:36 ` David Woodhouse
2007-06-28 12:20 ` Kyle Moffett
2007-06-28 3:06 ` Kyle McMartin
2007-06-28 0:30 ` Andi Kleen
2007-06-28 11:42 ` Kyle Moffett
2007-06-28 3:57 ` Matthew Wilcox [this message]
2007-06-28 11:53 ` Kyle Moffett
2007-06-28 12:08 ` Jakub Jelinek
2007-06-28 12:18 ` Kyle Moffett
2007-06-28 4:03 ` H. Peter Anvin
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=20070628035754.GB22063@parisc-linux.org \
--to=matthew@wil.cx \
--cc=bunk@stusta.de \
--cc=david@lang.hm \
--cc=dwmw2@infradead.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mrmacman_g4@mac.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