All of lore.kernel.org
 help / color / mirror / Atom feed
From: walter harms <WHarms@bfs.de>
To: kernel-janitors@vger.kernel.org
Subject: Re: any value to numerous checks of "#ifdef __GNUC__"?
Date: Fri, 04 Apr 2008 14:44:40 +0000	[thread overview]
Message-ID: <47F63ED8.9080505@bfs.de> (raw)
In-Reply-To: <alpine.LFD.1.00.0804040916040.24121@localhost.localdomain>



Robert P. J. Day wrote:
>   there are numerous header files that contain a check of the form
> 
>     #ifdef __GNUC__
> 
> but <linux/compiler.h> already insists on a GNU C-flavoured compiler:
> 
> #if __GNUC__ >= 4
> # include <linux/compiler-gcc4.h>
> #elif __GNUC__ = 3 && __GNUC_MINOR__ >= 2
> # include <linux/compiler-gcc3.h>
> #else
> # error Sorry, your compiler is too old/not recognized.
> #endif
> 
>   so is there any point in keeping all those checks around?  is it
> even remotely feasible that the kernel might someday support a non-GNU
> C compiler, given the numerous gcc extensions that are used?
> 
> rday
> --
> 

hi,
so far i know the intel compiler can compile a linux kernel.
ntl. this is most likely crap since the compiler is checked much more early.
(or at least should).
I only reason i can think of is that this module is used in other places outside
the linux kernle tree.

re,
 wh







  reply	other threads:[~2008-04-04 14:44 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-04 13:18 any value to numerous checks of "#ifdef __GNUC__"? Robert P. J. Day
2008-04-04 14:44 ` walter harms [this message]
2008-04-04 15:21 ` Robert P. J. Day
2008-04-04 15:28 ` Robert P. J. Day
2008-04-05  1:05 ` Darren Jenkins
2008-04-05 12:26 ` Robert P. J. Day

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=47F63ED8.9080505@bfs.de \
    --to=wharms@bfs.de \
    --cc=kernel-janitors@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.