From: Adrian Bunk <bunk@stusta.de>
To: kernel-janitors@vger.kernel.org
Subject: Re: [KJ] remove all content specific to GCC < 3.2??
Date: Thu, 07 Jun 2007 17:10:54 +0000 [thread overview]
Message-ID: <20070607171054.GO5500@stusta.de> (raw)
In-Reply-To: <Pine.LNX.4.64.0706071212280.29467@localhost.localdomain>
On Thu, Jun 07, 2007 at 12:17:42PM -0400, Robert P. J. Day wrote:
>
> is it relatively safe to strip the kernel tree of any content that
> is conditional upon unacceptably old versions of GCC?
>
> the header file linux/compiler.h already rejects the use of old gnu
> compilers:
>...
> so clearly any gcc < 3.2 is dead in the water, which suggests that any
> content dependent on that can be tossed as well. as a starting point,
> one can search for the macro __GNUC_MINOR__ to find:
>...
> seems like a lot of that can be removed. anyone want to deal with
> that if it seems like a viable project?
None of the lines you have quoted could be removed because they'd deal
with gcc < 3.2 (the compiler.h and init/main.c #error's should stay).
I already removed all #ifdef's dealing with gcc < 3.2 when the gcc
requirement was raised to 3.2
> rday
>...
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
_______________________________________________
Kernel-janitors mailing list
Kernel-janitors@lists.linux-foundation.org
https://lists.linux-foundation.org/mailman/listinfo/kernel-janitors
next prev parent reply other threads:[~2007-06-07 17:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-07 16:17 [KJ] remove all content specific to GCC < 3.2?? Robert P. J. Day
2007-06-07 17:10 ` Adrian Bunk [this message]
2007-06-07 17:29 ` Robert P. J. Day
2007-06-08 9:21 ` walter harms
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=20070607171054.GO5500@stusta.de \
--to=bunk@stusta.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.