mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jan-Benedict Glaw <jbglaw@lug-owl.de>
To: linux-kernel@vger.kernel.org
Subject: Re: [2.6 patch] remove support for gcc < 3.2
Date: Thu, 4 Aug 2005 08:54:47 +0200	[thread overview]
Message-ID: <20050804065447.GB25606@lug-owl.de> (raw)
In-Reply-To: <21d7e99705080318347d6b58d5@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1722 bytes --]

On Thu, 2005-08-04 11:34:27 +1000, Dave Airlie <airlied@gmail.com> wrote:
> On 8/1/05, Adrian Bunk <bunk@stusta.de> wrote:
> > This patch removes support for gcc < 3.2 .
> > 
> > The advantages are:
> > - reducing the number of supported gcc versions from 8 to 4 [1]
> >   allows the removal of several #ifdef's and workarounds
> > - my impression is that the older compilers are only rarely
> >   used, so miscompilations of a driver with an old gcc might
> >   not be detected for a longer amount of time
> > 
> >
> 
> Another disadvantage is you'll really piss of the VAX developers (all
> 3 of us!!!, well me not so much anymore...)
> 
> I think there is a gcc 4.x compiler nearly capable of building a
> kernel for the VAX...

-sh-3.00# cat cpuinfo
cpu             : VAX
cpu type        : KA43
cpu sid         : 0x0b000006
cpu sidex       : 0x04010002
page size       : 4096
BogoMIPS        : 10.08
-sh-3.00# cat version
Linux version 2.6.12 (jbglaw@d2) (gcc version 4.1.0 20050803 (experimental)) #2 Wed Aug 3 23:42:11 CEST 2005

Current GCC from CVS (plus minor configury patches) seems to work. We
had -fno-unit-at-a-time missing in our arch Makefile which hides a bug
in kernel's sources.

I guess that if you remove -fno-unit-at-a-time from i386 and use a
current GCC, you'll run into that fun, too.

MfG, JBG
PS: Yes, we lie about page size.

-- 
Jan-Benedict Glaw       jbglaw@lug-owl.de    . +49-172-7608481             _ O _
"Eine Freie Meinung in  einem Freien Kopf    | Gegen Zensur | Gegen Krieg  _ _ O
 fuer einen Freien Staat voll Freier Bürger" | im Internet! |   im Irak!   O O O
ret = do_actions((curr | FREE_SPEECH) & ~(NEW_COPYRIGHT_LAW | DRM | TCPA));

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2005-08-04  6:54 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-31 22:26 Adrian Bunk
2005-07-31 22:36 ` David S. Miller
2005-07-31 23:08   ` Nigel Cunningham
2005-08-07 16:25   ` Denis Vlasenko
2005-08-10 19:40   ` Bill Davidsen
2005-08-11  0:02     ` Joe
2005-08-11  0:05       ` David S. Miller
2005-08-13  3:27       ` Bill Davidsen
2005-08-01  3:01 ` [2.6 patch] " Kurt Wall
2005-08-02  5:37   ` Willy Tarreau
2005-08-01  4:27 ` Miles Bader
2005-08-02 21:46 ` Jan-Benedict Glaw
2005-08-03  2:08 ` Gustavo Guillermo Pérez
2005-08-04  0:53   ` Mathieu Chouquet-Stringer
2005-08-04 20:34     ` networking problems when using gcc 4.0.1 Adrian Bunk
2005-08-04  1:34 ` [2.6 patch] remove support for gcc < 3.2 Dave Airlie
2005-08-04  6:54   ` Jan-Benedict Glaw [this message]
2005-08-04 20:38     ` Adrian Bunk
2005-08-05 21:14       ` Jan-Benedict Glaw
2005-08-05 21:30         ` Martin Drab
2005-08-05 21:37           ` Jan-Benedict Glaw
2005-08-13  9:21       ` Jan-Benedict Glaw
2005-08-12  7:40     ` Geert Uytterhoeven
2005-08-12 10:40       ` Maciej W. Rozycki
2005-08-12 12:29       ` Jan-Benedict Glaw

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=20050804065447.GB25606@lug-owl.de \
    --to=jbglaw@lug-owl.de \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®