All of lore.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: Adrian Bunk <bunk@stusta.de>
Cc: Harvey Harrison <harvey.harrison@gmail.com>,
	linux-kernel@vger.kernel.org,
	Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [2.6 patch] asm-generic/int-ll64.h: always provide __{s,u}64
Date: Tue, 20 May 2008 07:54:18 -0700	[thread overview]
Message-ID: <4832E61A.3080009@zytor.com> (raw)
In-Reply-To: <20080520090949.GI17716@cs181133002.pp.htv.fi>

Adrian Bunk wrote:
> 
> $ cat test.c
> #include <stdio.h>
> 
> int main()
> {
> #ifdef __i486__
>   printf("foobarbaz\n");
> #endif
> 
>   return 0;
> }

*Groan* you're right.  Blitering idiots... they only present __i386__ 
and whatever *exact* CPU you have -march= for, which of course is a 
*CHANGING SET* (just __i486__, __i586__ and __i686__ isn't enough... 
they seem to also have __core2__, __k8__ and $DEITY knows what else.)

The only sensible way to handle that would be to centralize that 
knowledge in a header file.

	-hpa

      reply	other threads:[~2008-05-20 15:01 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-19 21:54 [2.6 patch] asm-generic/int-ll64.h: always provide __{s,u}64 Adrian Bunk
2008-05-19 22:01 ` H. Peter Anvin
2008-05-19 22:27   ` Harvey Harrison
2008-05-19 22:29     ` H. Peter Anvin
2008-05-19 22:32     ` Adrian Bunk
2008-05-19 23:51       ` H. Peter Anvin
2008-05-20  0:13         ` Adrian Bunk
2008-05-20  0:17           ` H. Peter Anvin
2008-05-20  0:33             ` Adrian Bunk
2008-05-20  1:16               ` H. Peter Anvin
2008-05-20  9:09                 ` Adrian Bunk
2008-05-20 14:54                   ` 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=4832E61A.3080009@zytor.com \
    --to=hpa@zytor.com \
    --cc=akpm@linux-foundation.org \
    --cc=bunk@stusta.de \
    --cc=harvey.harrison@gmail.com \
    --cc=linux-kernel@vger.kernel.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.