From: Arnd Bergmann <arnd-r2nGTMty4D4@public.gmane.org>
To: Roland McGrath <roland-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Cc: "H. Peter Anvin" <hpa-YMNOUZJC4hwAvxtiuMwx3w@public.gmane.org>,
Will Newton <will.newton-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
Geert Uytterhoeven
<geert.uytterhoeven-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
michal.simek-g5w7nrANp4BDPfheJLI6IQ@public.gmane.org,
Linux Kernel list
<linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
linux-arch-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-api-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Chen Liqin <liqin.chen-+XGAvkf1AAHby3iVrkZq2A@public.gmane.org>
Subject: Re: [RFC] asm-generic/{unistd,types,posix_types}.h for new arch
Date: Thu, 2 Apr 2009 15:06:12 +0200 [thread overview]
Message-ID: <200904021506.13942.arnd@arndb.de> (raw)
In-Reply-To: <20090401213219.7B324FC3AB-nL1rrgvulkc2UH6IwYuUx0EOCMrvLtNR@public.gmane.org>
On Wednesday 01 April 2009, Roland McGrath wrote:
> > Actually, gcc does have the _LP64 and __SIZEOF_POINTER__ macros (as well
> > as __CHAR_BIT__), although I don't know how far back it does have that.
> > If it has been with us for long enough it might be possible to
> > switch over to using panarch macros.
For user space, we also need to consider non-gcc compilers that could have
a different set of macros. As long as we don't start relying on any new
ones besides those we already use (__x86_64__, __s390x__, __powerpc64__,
__mips64, __arch64__), we at least don't break anything accidentally.
> Worst case the oldest compilers had <limits.h> and
> "#if ULONG_MAX == 0xffffffffUL", though I wouldn't like
> myself to be using a setup where <limits.h> got pulled in.
That would of course work with non-gcc, but we are really not allowed
to pull in <limits.h> from places like <types.h> where it would be needed
then.
Arnd <><
--
To unsubscribe from this list: send the line "unsubscribe linux-api" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
WARNING: multiple messages have this Message-ID (diff)
From: Arnd Bergmann <arnd@arndb.de>
To: Roland McGrath <roland@redhat.com>
Cc: "H. Peter Anvin" <hpa@zytor.com>,
Will Newton <will.newton@gmail.com>,
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: Thu, 2 Apr 2009 15:06:12 +0200 [thread overview]
Message-ID: <200904021506.13942.arnd@arndb.de> (raw)
Message-ID: <20090402130612.1fOxjH9z4U5OJ68iIN_9IOC_LuZqQYMWyNEUFxB9QMw@z> (raw)
In-Reply-To: <20090401213219.7B324FC3AB@magilla.sf.frob.com>
On Wednesday 01 April 2009, Roland McGrath wrote:
> > Actually, gcc does have the _LP64 and __SIZEOF_POINTER__ macros (as well
> > as __CHAR_BIT__), although I don't know how far back it does have that.
> > If it has been with us for long enough it might be possible to
> > switch over to using panarch macros.
For user space, we also need to consider non-gcc compilers that could have
a different set of macros. As long as we don't start relying on any new
ones besides those we already use (__x86_64__, __s390x__, __powerpc64__,
__mips64, __arch64__), we at least don't break anything accidentally.
> Worst case the oldest compilers had <limits.h> and
> "#if ULONG_MAX == 0xffffffffUL", though I wouldn't like
> myself to be using a setup where <limits.h> got pulled in.
That would of course work with non-gcc, but we are really not allowed
to pull in <limits.h> from places like <types.h> where it would be needed
then.
Arnd <><
next prev parent reply other threads:[~2009-04-02 13:06 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-30 7:15 Removing __kernel_old_uid_t, git_t, dev_t Michal Simek
2009-03-30 13:58 ` Arnd Bergmann
2009-03-30 14:41 ` Geert Uytterhoeven
[not found] ` <10f740e80903300741h387e6342veba0ccceea6714e9-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-03-30 15:17 ` Arnd Bergmann
2009-03-30 15:17 ` Arnd Bergmann
[not found] ` <200903301717.57184.arnd-r2nGTMty4D4@public.gmane.org>
2009-03-30 21:11 ` David Miller
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-03-31 0:26 ` Arnd Bergmann
2009-04-01 14:11 ` [RFC] asm-generic/{unistd,types,posix_types}.h for new arch Arnd Bergmann
2009-04-01 14:11 ` Arnd Bergmann
[not found] ` <200904011611.53355.arnd-r2nGTMty4D4@public.gmane.org>
2009-04-01 14:39 ` Will Newton
2009-04-01 14:39 ` Will Newton
2009-04-01 15:04 ` Arnd Bergmann
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 [this message]
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=200904021506.13942.arnd@arndb.de \
--to=arnd-r2ngtmty4d4@public.gmane.org \
--cc=geert.uytterhoeven-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=hpa-YMNOUZJC4hwAvxtiuMwx3w@public.gmane.org \
--cc=linux-api-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-arch-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=liqin.chen-+XGAvkf1AAHby3iVrkZq2A@public.gmane.org \
--cc=michal.simek-g5w7nrANp4BDPfheJLI6IQ@public.gmane.org \
--cc=roland-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=will.newton-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.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.