public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <ak@muc.de>
To: Adrian Bunk <bunk@stusta.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [2.6 patch] add compiler-gcc4.h
Date: Sun, 30 Jan 2005 15:11:19 +0100	[thread overview]
Message-ID: <m1pszn3t2w.fsf@muc.de> (raw)
In-Reply-To: <20050130130308.GK3185@stusta.de> (Adrian Bunk's message of "Sun, 30 Jan 2005 14:03:08 +0100")

Adrian Bunk <bunk@stusta.de> writes:

> With the release of gcc 4.0 being only a few months away and people 
> already tring compiling with it, it's time for adding a compiler-gcc4.h .
>
> This patch contains the following changes:
> - compiler-gcc+.h: add the missing noinline and __compiler_offsetof
> - compiler-gcc4.h: new file based on the corrected compiler-gcc+.h
> - compiler.h: include compiler-gcc4.h for gcc 4
> - compiler-gcc3.h: remove __compiler_offsetof (there will never be a
>                                                gcc 3.5)
>                    small indention corrections

I don't think it makes much sense right now because it's basically
identical to compiler-gcc3.h. I would only add it where there is a 
need for a real difference.

-Andi

  reply	other threads:[~2005-01-30 14:11 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-30 13:03 [2.6 patch] add compiler-gcc4.h Adrian Bunk
2005-01-30 14:11 ` Andi Kleen [this message]
2005-01-30 14:14   ` Adrian Bunk
2005-01-30 15:35   ` Matthias-Christian Ott
2005-02-03  1:04     ` H. Peter Anvin
2005-02-05 13:50       ` Adrian Bunk
2005-02-05 18:45         ` H. Peter Anvin
2005-02-05 19:38           ` Adrian Bunk
2005-02-05 19:52             ` H. Peter Anvin
2005-02-06  0:43               ` [RFC][PATCH-2.6] Clean up and merge compiler-*.h Kyle Moffett
2005-02-06  0:50               ` [2.6 patch] add compiler-gcc4.h Adrian Bunk

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=m1pszn3t2w.fsf@muc.de \
    --to=ak@muc.de \
    --cc=bunk@stusta.de \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox