public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: maximilian attems <maks@sternwelten.at>
Cc: linux-kernel@vger.kernel.org, klibc list <klibc@zytor.com>
Subject: Re: [PATCH] klibc
Date: Sat, 03 Jun 2006 15:26:05 -0700	[thread overview]
Message-ID: <44820C7D.6080501@zytor.com> (raw)
In-Reply-To: <20060602081416.GA11358@nancy>

maximilian attems wrote:
> On Thu, 01 June 2006, H. Peter Anvin wrote:
>> Brian F. G. Bidulock wrote:
>>> On Thu, 01 Jun 2006, Bob Picco wrote:
>>>>  
>>>> -#if !defined(__x86_64__) && !defined(__ia64__) && !defined(__sparc_v9__)
>>>> +#if !defined(__x86_64__) && !defined(__ia64__) && !defined(__sparc_v9__) && \
>>>> +	!defined(__powerpc64__)
>>> Why not just !defined(__LP64__) ?
>> _BITSIZE == 64 is really the right formula... if I remember correctly, there were some 
>> 64-bit platforms (Alpha?) which didn't conform, though.  I will look at this later today.
>>
>> 	-hpa
> 
> indeed aboves line contains an mistake by an earlier patch of mine.
> 
> -#if !defined(__x86_64__) && !defined(__ia64__) && !defined(__sparc_v9__)
> +#if !defined(__x86_64__) && !defined(__ia64__) && !defined(__arch64__)
> 
> is atm needed to get statfs right on sparc.
> 

__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.

	-hpa

  reply	other threads:[~2006-06-03 22:26 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 [this message]
2006-06-04  6:30         ` David Miller
2006-06-04 17:42           ` H. Peter Anvin

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=44820C7D.6080501@zytor.com \
    --to=hpa@zytor.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox