From: Oleg Verych <olecom@flower.upol.cz>
To: linux-kernel@vger.kernel.org
Subject: Re: why test for "__GNUC__"?
Date: Sun, 29 Oct 2006 16:17:51 +0000 (UTC) [thread overview]
Message-ID: <slrnek9le5.2vm.olecom@flower.upol.cz> (raw)
In-Reply-To: Pine.LNX.4.64.0610291044230.9726@localhost.localdomain
Hallo.
On 2006-10-29, Robert P. J. Day wrote:
> On Sun, 29 Oct 2006, Alexey Dobriyan wrote:
>
>> On Sun, Oct 29, 2006 at 07:44:18AM -0500, Robert P. J. Day wrote:
>> > p.s. is there, in fact, any part of the kernel source tree that has a
>> > preprocessor directive to identify the use of ICC? just curious.
>>
>> Please, do
>>
>> ls include/linux/compiler-*
>
> but according to compiler.h:
>
> /* Intel compiler defines __GNUC__. So we will overwrite implementations
> * coming from above header files here
> */
>
> so even ICC will define __GNUC__, which means that testing for
> __GNUC__ is *still*, under the circumstances, redundant, isn't that
> right?
Does it introduce bugs? Just think of it as legacy, if you want.
And if you can, please, help with development or bugs, not this.
____
next prev parent reply other threads:[~2006-10-29 16:18 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-29 11:13 why test for "__GNUC__"? Robert P. J. Day
2006-10-29 11:44 ` Jan Engelhardt
2006-10-29 12:44 ` Robert P. J. Day
2006-10-29 12:05 ` Alexey Dobriyan
2006-10-29 15:48 ` Robert P. J. Day
2006-10-29 16:17 ` Oleg Verych [this message]
2006-10-29 17:18 ` Adrian Bunk
2006-10-29 17:37 ` Robert P. J. Day
2006-10-29 18:23 ` Oleg Verych
2006-10-30 3:38 ` Adrian Bunk
2006-10-30 5:08 ` Kyle Moffett
2006-10-29 16:59 ` Valdis.Kletnieks
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=slrnek9le5.2vm.olecom@flower.upol.cz \
--to=olecom@flower.upol.cz \
--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.