linux-kernel - Re: why test for "__GNUC_

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <Pine.LNX.4.64.0610290742310.7457@localhost.localdomain>
Date:	Sun, 29 Oct 2006 07:44:18 -0500 (EST)
From:	"Robert P. J. Day" <rpjday@...dspring.com>
To:	Jan Engelhardt <jengelh@...ux01.gwdg.de>
cc:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: why test for "__GNUC__"?

On Sun, 29 Oct 2006, Jan Engelhardt wrote:

>
> >  since (as i understand it) the linux kernel *requires* gcc these
> >days, what is the point of the numerous preprocessor tests of the
> >form:
>
> ICC is said to work too.

ah, i was not aware of that.  but does that mean that ICC is (or will
be) *officially* supported?  or does it just *happen* to work at the
moment with no guarantees of future compatibility?

rday

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.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/