From: Arjan van de Ven <arjanv@redhat.com>
To: Gabriel Paubert <paubert@iram.es>
Cc: linux-kernel@vger.kernel.org, torvalds@osdl.org, akpm@osdl.org
Subject: Re: using gcc built-ins for bitops?
Date: Thu, 24 Jun 2004 14:21:18 +0200 [thread overview]
Message-ID: <20040624122118.GB21376@devserv.devel.redhat.com> (raw)
In-Reply-To: <20040624115146.GA7513@iram.es>
[-- Attachment #1: Type: text/plain, Size: 695 bytes --]
On Thu, Jun 24, 2004 at 01:51:46PM +0200, Gabriel Paubert wrote:
> > --- linux-2.6.7/include/linux/compiler-gcc3.h~ 2004-06-24 09:26:04.123455290 +0200
> > +++ linux-2.6.7/include/linux/compiler-gcc3.h 2004-06-24 09:26:04.123455290 +0200
> > @@ -19,6 +19,11 @@
> > # define __attribute_used__ __attribute__((__unused__))
> > #endif
> >
> > +#if __GNUC_MINOR__ >= 4
>
> Please do no test only on minor. People have been arguing
> whether the next major release of GCC should be called 3.5
> or 4.0 since tree-ssa has been merged.
this header is only uses for the gcc major == 3. The header for ==4 and
later has the define unconditional, and the file for major ==2 doesn't have
it at all.
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-06-24 12:21 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-24 7:09 using gcc built-ins for bitops? Arjan van de Ven
2004-06-24 9:00 ` Andrew Morton
2004-06-24 9:06 ` Arjan van de Ven
2004-06-24 13:41 ` Ben Collins
2004-06-24 9:17 ` Arjan van de Ven
2004-06-24 11:31 ` Arjan van de Ven
2004-06-24 12:05 ` Jakub Jelinek
2004-06-24 12:35 ` Arjan van de Ven
2004-06-24 15:30 ` Linus Torvalds
2004-06-24 9:31 ` Paul Jackson
2004-06-24 10:36 ` Jakub Jelinek
2004-06-24 15:25 ` Linus Torvalds
2004-06-24 11:51 ` Gabriel Paubert
2004-06-24 12:21 ` Arjan van de Ven [this message]
[not found] <2awGH-DF-17@gated-at.bofh.it>
2004-06-24 13:46 ` Pascal Schmidt
2004-06-24 13:49 ` Arjan van de Ven
2004-06-24 13:51 ` Pascal Schmidt
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=20040624122118.GB21376@devserv.devel.redhat.com \
--to=arjanv@redhat.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=paubert@iram.es \
--cc=torvalds@osdl.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.