All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Martin J. Bligh" <mbligh@aracnet.com>
To: Tom Rini <trini@kernel.crashing.org>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: post-halloween 0.2
Date: Wed, 30 Oct 2002 11:57:58 -0800	[thread overview]
Message-ID: <770420000.1036007878@flay> (raw)
In-Reply-To: <20021030195034.GA27472@opus.bloom.county>

>> > Can you also mention not using gcc 3.0.x (stack pointer handling bug)
>> 
>> Any chance of putting this sort of thing as #error detection
>> in the compile so it auto-breaks? I seem to recall that's done
>> for some versions of GCC already ...
> 
> And what arch is that for?  Adding a nice facility for per-arch (and
> maybe global) compiler / binutils testing would be nice, if we're going
> to go down that road..

Alan, would you consider something like (TOTALLY untested):

diff -purN -X /home/mbligh/.diff.exclude virgin/init/main.c gcc/init/main.c
--- virgin/init/main.c	Fri Oct 18 21:01:16 2002
+++ gcc/init/main.c	Wed Oct 30 11:54:54 2002
@@ -50,7 +50,7 @@
  * To avoid associated bogus bug reports, we flatly refuse to compile
  * with a gcc that is known to be too old from the very beginning.
  */
-#if __GNUC__ < 2 || (__GNUC__ == 2 && __GNUC_MINOR__ < 91)
+#if __GNUC__ < 2 || (__GNUC__ == 2 && __GNUC_MINOR__ < 91) || (__GNUC__ == 3 && __GNUC_MINOR__ == 0)
 #error Sorry, your GCC is too old. It builds incorrect kernels.
 #endif
 
If you like it, I'll get it tested.

Probably some things are per-arch and some are global, at a guess.
Currently we have:

init/main.c:
/*
 * Versions of gcc older than that listed below may actually compile
 * and link okay, but the end product can have subtle run time bugs.
 * To avoid associated bogus bug reports, we flatly refuse to compile
 * with a gcc that is known to be too old from the very beginning.
 */
#if __GNUC__ < 2 || (__GNUC__ == 2 && __GNUC_MINOR__ < 91)
#error Sorry, your GCC is too old. It builds incorrect kernels.
#endif

arch/arm/kernel/asm-offsets.c 

/*
 * Make sure that the compiler and target are compatible.
 */
#if defined(__APCS_32__) && defined(CONFIG_CPU_26)
#error Sorry, your compiler targets APCS-32 but this kernel requires APCS-26
#endif
#if defined(__APCS_26__) && defined(CONFIG_CPU_32)
#error Sorry, your compiler targets APCS-26 but this kernel requires APCS-32
#endif
#if __GNUC__ < 2 || (__GNUC__ == 2 && __GNUC_MINOR__ < 95)
#error Sorry, your compiler is known to miscompile kernels.  Only use gcc 2.95.3
 and later.
#endif
#if __GNUC__ == 2 && __GNUC_MINOR__ == 95
/* shame we can't detect the .1 or .2 releases */
#warning GCC 2.95.2 and earlier miscompiles kernels.
#endif



  reply	other threads:[~2002-10-30 19:59 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-30 17:11 post-halloween 0.2 Dave Jones
2002-10-30 18:47 ` Ian Soboroff
2002-10-30 18:52   ` Greg KH
2002-10-30 19:02     ` Ian Soboroff
2002-10-30 19:08       ` Greg KH
2002-10-30 19:13       ` Patrick Mochel
2002-10-30 19:16         ` Ian Soboroff
2002-10-30 19:23           ` Patrick Mochel
2002-10-30 19:17         ` Ian Soboroff
2002-10-30 19:33 ` Alan Cox
2002-10-30 19:17   ` Martin J. Bligh
2002-10-30 19:50     ` Tom Rini
2002-10-30 19:57       ` Martin J. Bligh [this message]
2002-10-30 20:23         ` Tom Rini
2002-10-30 20:50         ` Arador
2002-10-30 21:03           ` Martin J. Bligh
2002-10-31  0:12         ` Alan Cox
2002-10-31  0:47   ` Dave Jones
2002-10-31 11:48     ` Alan Cox
2002-11-01  1:29       ` Bill Davidsen
2002-10-30 23:09 ` Pavel Machek
2002-10-31  0:35 ` Skip Ford
2002-10-31  6:27 ` Htree ate my hard drive, was: " Duncan Sands
2002-10-31  8:07   ` Andreas Dilger
2002-10-31  8:20     ` Duncan Sands
2002-11-04 22:42     ` [Ext2-devel] " Stephen C. Tweedie
2002-11-04 22:59       ` Duncan Sands
2002-11-04 23:22       ` Udo A. Steinberg
2002-10-31 23:05   ` Mike Civil
2002-11-03 20:42     ` Duncan Sands
2002-11-03 22:00       ` Mike Civil
2002-11-03 22:11   ` Martin Waitz
2002-11-07 15:36 ` Jan Kara
2002-11-07 15:44   ` Dave Jones

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=770420000.1036007878@flay \
    --to=mbligh@aracnet.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=trini@kernel.crashing.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.