From: "H. Peter Anvin" <hpa@zytor.com>
To: David Miller <davem@davemloft.net>
Cc: maks@sternwelten.at, linux-kernel@vger.kernel.org, klibc@zytor.com
Subject: Re: [PATCH] klibc
Date: Sun, 04 Jun 2006 10:42:39 -0700 [thread overview]
Message-ID: <44831B8F.2060205@zytor.com> (raw)
In-Reply-To: <20060603.233034.59468148.davem@davemloft.net>
David Miller wrote:
>
>> __arch64__ is ugly; it doesn't say it's a sparc thing. I have added
>> -D__sparc_v9__ to the sparc64 MCONFIG file, so I think that's fine.
>>
>> Perhaps the right thing to do is to make this an archconfig.h configurable.
>
> Please don't do this, I'll explain why.
>
> Using __sparc_v9__ is incorrect, here is the lowdown on these defines:
>
> 1) __sparc_v9__ means "-mcpu={ultrasparc*,niagara}" or "-mcpu=v9".
> Although this is implied by "-m64" it can be used for 32-bit
> code too.
>
> __sparc_v9__ means "using v9 instructions" which does not
> necessarily mean 64-bit
>
> 2) "__sparc__ && __arch64__" means 64-bit sparc
>
> People often get this wrong, and it certainly is confusing.
>
Okay, how about __sparc64__ then (via -D in the MCONFIG file.)
I did change this particular instance to be a archconfig variable, so it
doesn't exist (I try very much to avoid architecture-specific #ifdefs in
bulk code.)
-hpa
prev parent reply other threads:[~2006-06-04 17:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-01 19:47 [PATCH] klibc Bob Picco
2006-06-01 20:06 ` Brian F. G. Bidulock
2006-06-01 20:23 ` H. Peter Anvin
2006-06-02 8:14 ` maximilian attems
2006-06-03 22:26 ` H. Peter Anvin
2006-06-04 6:30 ` David Miller
2006-06-04 17:42 ` H. Peter Anvin [this message]
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=44831B8F.2060205@zytor.com \
--to=hpa@zytor.com \
--cc=davem@davemloft.net \
--cc=klibc@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maks@sternwelten.at \
/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.