From: Paul Mackerras <paulus@linuxcare.com>
To: Jeff Garzik <jgarzik@mandrakesoft.com>,
Michael Meissner <meissner@cygnus.com>
Cc: Linux/PPC Developer list <linuxppc-dev@lists.linuxppc.org>
Subject: Re: PPC should not use -fno-builtin (was Re: 2.3.47 imac build?)
Date: Tue, 29 Feb 2000 11:49:03 +1100 [thread overview]
Message-ID: <00022911542401.10645@argo.linuxcare.com.au> (raw)
In-Reply-To: 38BAF958.E31D88A3@mandrakesoft.com
On Tue, 29 Feb 2000, Jeff Garzik wrote:
> That is the crux of the matter.... In the PPC arch, size_t is
> unconditionally the same whether you have a 32-bit or 64-bit procesor...
Well, no... unsigned long is 32 bits wide when compiling for 32-bit
machines, 64 bits wide when compiling for 64-bit machines.
Anyway, I have caved in and put the following ugliness in
asm-ppc/posix-types.h:
#include <linux/config.h> /* for CONFIG_PPC64 */
[snip]
/* Grrr... gcc thinks size_t is unsigned int, so we either
have to have this nonsense or use -fno-builtin. - paulus */
#ifdef CONFIG_PPC64
typedef unsigned long __kernel_size_t;
typedef long __kernel_ssize_t;
#else
typedef unsigned int __kernel_size_t;
typedef int __kernel_ssize_t;
#endif /* CONFIG_PPC64 */
My linuxcare.com.au::linux-pmac-devel rsync tree is now up to 2.3.48, BTW.
--
Paul Mackerras, Senior Open Source Researcher, Linuxcare, Inc.
+61 2 6262 8990 tel, +61 2 6262 8991 fax
paulus@linuxcare.com.au, http://www.linuxcare.com.au/
Linuxcare. Support for the revolution.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next parent reply other threads:[~2000-02-29 0:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <38BAF958.E31D88A3@mandrakesoft.com>
2000-02-29 0:49 ` Paul Mackerras [this message]
2000-02-29 17:03 ` PPC should not use -fno-builtin (was Re: 2.3.47 imac build?) Michael Schmitz
2000-02-29 17:51 ` Jeff Garzik
2000-02-29 18:24 ` Benjamin Herrenschmidt
2000-02-29 19:21 ` Michael Schmitz
2000-02-29 23:07 ` Andreas Tobler
2000-03-01 8:49 ` Michael Schmitz
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=00022911542401.10645@argo.linuxcare.com.au \
--to=paulus@linuxcare.com \
--cc=jgarzik@mandrakesoft.com \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=meissner@cygnus.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).