From: Jan-Benedict Glaw <jbglaw@lug-owl.de>
To: Adrian Bunk <bunk@stusta.de>
Cc: Andrew Morton <akpm@osdl.org>, linux-kernel@vger.kernel.org
Subject: Re: [2.6 patch] remove support for gcc < 3.2
Date: Tue, 2 Aug 2005 23:46:22 +0200 [thread overview]
Message-ID: <20050802214622.GD5787@lug-owl.de> (raw)
In-Reply-To: <20050731222606.GL3608@stusta.de>
[-- Attachment #1: Type: text/plain, Size: 1939 bytes --]
On Mon, 2005-08-01 00:26:07 +0200, 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
[...]
> [1] support removed: 2.95, 2.96, 3.0, 3.1
> still supported: 3.2, 3.3, 3.4, 4.0
This patch in mind, I built the vax-linux kernel again with gcc-HEAD
(gcc-4.1) and it blew off in:
$ make V=1 ARCH=vax CROSS_COMPILE=vax-linux- mopboot
[...]
vax-linux-gcc -Wp,-MD,init/.initramfs.o.d -nostdinc -isystem /home/jbglaw/vax-linux/scm/build-20050802-171439-vax-linux/install/usr/lib/gcc/vax-linux/4.1.0/include -D__KERNEL__ -Iinclude -Wall -Wstrict-prototypes -Wno-trigraphs -fno-strict-aliasing -fno-common -ffreestanding -O1 -fomit-frame-pointer -pipe -Wdeclaration-after-statement -Wno-pointer-sign -DKBUILD_BASENAME=initramfs -DKBUILD_MODNAME=initramfs -c -o init/initramfs.o init/initramfs.c
init/initramfs.c:10: error: message causes a section type conflict
init/initramfs.c:33: error: head causes a section type conflict
init/initramfs.c:80: error: ino causes a section type conflict
init/initramfs.c:80: error: major causes a section type conflict
[...]
Adding -fno-unit-at-a-time fixed this, but from what Google found, this
is actually a bug in the C sources: the __initdata variables are to be
put into a read-only segment but are missing a const qualifyer, so
-fno-unit-at-a-time seems to hide a bug here.
Could somebody comment on this? Or shall I open a bug report for GCC?
MfG, JBG
--
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 --]
next prev parent reply other threads:[~2005-08-02 21:46 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-31 22:26 [2.6 patch] remove support for gcc < 3.2 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 [this message]
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
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=20050802214622.GD5787@lug-owl.de \
--to=jbglaw@lug-owl.de \
--cc=akpm@osdl.org \
--cc=bunk@stusta.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 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.