From: Segher Boessenkool <segher@kernel.crashing.org>
To: Jon Loeliger <jdl@freescale.com>
Cc: linuxppc64-dev <linuxppc64-dev@ozlabs.org>,
"linuxppc-dev@ozlabs.org" <linuxppc-dev@ozlabs.org>
Subject: Re: [PATCH] 1/2 Start header file merger (Was: Re: Beginning Merger Patch)
Date: Mon, 29 Aug 2005 17:44:34 +0200 [thread overview]
Message-ID: <7d30f9ea7e93320d569a60c90f179ba5@kernel.crashing.org> (raw)
In-Reply-To: <1125089709.32488.35.camel@cashmere.sps.mot.com>
> Anyone care to take a semi-authoritative stand on what
> symbol to use to distinguish 32/64-bit-ness in the
> include files?
It depends on what you are testing for.
Sometimes __LP64__ would be best (when you want to know
the size of pointers etc.), sometimes __powerpc64__ (when
you need to know the available instruction set), and
I'm sure there are cases where you should use a different
symbol altogether, because you are testing something else.
Segher
next prev parent reply other threads:[~2005-08-29 15:44 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-02 22:59 Beginning Merger Patch Jon Loeliger
2005-08-02 23:05 ` Eugene Surovegin
2005-08-02 23:12 ` Dan Malek
2005-08-02 23:17 ` Eugene Surovegin
2005-08-03 3:08 ` Paul Mackerras
2005-08-03 2:38 ` Josh Boyer
2005-08-02 23:10 ` Dan Malek
2005-08-05 7:47 ` [PATCH] 1/2 Start header file merger (Was: Re: Beginning Merger Patch) Stephen Rothwell
2005-08-05 7:50 ` [PATCH] 2/2 merge the easy ones Stephen Rothwell
2005-08-05 8:37 ` [PATCH] 1/2 Start header file merger (Was: Re: Beginning Merger Patch) Stephen Rothwell
2005-08-05 9:08 ` Michael Ellerman
2005-08-05 11:53 ` Arnd Bergmann
2005-08-05 14:59 ` Stephen Rothwell
2005-08-05 16:24 ` Arnd Bergmann
2005-08-26 20:55 ` Jon Loeliger
2005-08-29 15:44 ` Segher Boessenkool [this message]
2005-08-29 18:41 ` Christopher Friesen
2005-08-17 5:39 ` Kumar Gala
2005-08-17 11:05 ` Arnd Bergmann
2005-08-03 2:17 ` Beginning Merger Patch Nathan Lynch
2005-08-03 2:58 ` Eugene Surovegin
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=7d30f9ea7e93320d569a60c90f179ba5@kernel.crashing.org \
--to=segher@kernel.crashing.org \
--cc=jdl@freescale.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=linuxppc64-dev@ozlabs.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;
as well as URLs for NNTP newsgroup(s).