From: Arnd Bergmann <arnd@arndb.de>
To: Will Newton <will.newton@gmail.com>
Cc: Geert Uytterhoeven <geert.uytterhoeven@gmail.com>,
michal.simek@petalogix.com,
Linux Kernel list <linux-kernel@vger.kernel.org>,
linux-arch@vger.kernel.org, linux-api@vger.kernel.org,
Chen Liqin <liqin.chen@sunplusct.com>
Subject: Re: [RFC] asm-generic/{unistd,types,posix_types}.h for new arch
Date: Wed, 1 Apr 2009 17:04:12 +0200 [thread overview]
Message-ID: <200904011704.13581.arnd@arndb.de> (raw)
In-Reply-To: <87a5b0800904010739g3564eb1fhf32afcfee4936c4b@mail.gmail.com>
On Wednesday 01 April 2009, Will Newton wrote:
> > + * There seems to be no way of detecting this automatically from user
> > + * space, so 64 bit architectures should override this in their types.h.
> > + */
> > +#ifndef __BITS_PER_LONG
> > +#define __BITS_PER_LONG 32
> > +#endif
>
> Why is this define required? It doesn't seem to be in any existing headers.
Unfortunately, there is no generic way to detect the word size yet,
but every architecture uses its own preprocessor macro (__x86_64__,
__s390x__, __ppc64__). We also can't use CONFIG_64BIT in an user-exported
interface header file, because the use space can also be compiled for
32 bits when the kernel uses 64 bits.
__BITS_PER_LONG is actually defined in parisc now, and was the result
of the last time we had this discussion. I'm still thinking about
making a separate <asm/bitsperlong.h> header, or a <asm/bits.h> that
also contains the respective __BIG_ENDIAN/__LITTLE_ENDIAN macros
which have the same problem. The advantage would be that other header
files (e.g. unistd.h) can known the word size without getting the
whole types.h name space.
Arnd <><
next prev parent reply other threads:[~2009-04-01 15:04 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <49D071A8.4010703@petalogix.com>
2009-03-30 13:58 ` Removing __kernel_old_uid_t, git_t, dev_t Arnd Bergmann
2009-03-30 14:41 ` Geert Uytterhoeven
[not found] ` <10f740e80903300741h387e6342veba0ccceea6714e9-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-03-30 15:17 ` Arnd Bergmann
[not found] ` <200903301717.57184.arnd-r2nGTMty4D4@public.gmane.org>
2009-03-30 21:11 ` David Miller
[not found] ` <20090330.141156.62568451.davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org>
2009-03-31 0:26 ` Arnd Bergmann
2009-04-01 14:11 ` [RFC] asm-generic/{unistd,types,posix_types}.h for new arch Arnd Bergmann
[not found] ` <200904011611.53355.arnd-r2nGTMty4D4@public.gmane.org>
2009-04-01 14:39 ` Will Newton
2009-04-01 15:04 ` Arnd Bergmann [this message]
2009-04-01 21:20 ` H. Peter Anvin
2009-04-01 21:32 ` Roland McGrath
[not found] ` <20090401213219.7B324FC3AB-nL1rrgvulkc2UH6IwYuUx0EOCMrvLtNR@public.gmane.org>
2009-04-02 13:06 ` Arnd Bergmann
2009-04-01 17:55 ` 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=200904011704.13581.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=geert.uytterhoeven@gmail.com \
--cc=linux-api@vger.kernel.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=liqin.chen@sunplusct.com \
--cc=michal.simek@petalogix.com \
--cc=will.newton@gmail.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;
as well as URLs for NNTP newsgroup(s).