From: "J.A. Magallon" <jamagallon@able.es>
To: Lista Linux-Kernel <linux-kernel@vger.kernel.org>
Subject: gcc-3.3.2 vs 2.6.0-test11
Date: Wed, 17 Dec 2003 12:37:42 +0100 [thread overview]
Message-ID: <20031217113742.GC2074@werewolf.able.es> (raw)
hi all..
Are there any known issues wrt gcc-3.3.2 ?
I built test11 with gcc-3.3.1 and worked fine, the same config built with
3.3.2 does not pass init launch:
INIT version 2.85 booting
and nothing more....
I have to check, but I think it also miscompiles 2.4. I rebuilt a kernel on a
remote box (2.4.23 + assorted patches), that worked fine under 3.3.1, and
after reboot the box didn't came to life, no ping.
TIA
--
J.A. Magallon <jamagallon()able!es> \ Software is like sex:
werewolf!able!es \ It's better when it's free
Mandrake Linux release 10.0 (Cooker) for i586
Linux 2.6.0-test11-jam2 (gcc 3.3.1 (Mandrake Linux 9.2 3.3.1-4mdk))
next reply other threads:[~2003-12-17 11:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-17 11:37 J.A. Magallon [this message]
2003-12-17 12:07 ` gcc-3.3.2 vs 2.6.0-test11 Andrew Walrond
2003-12-17 12:25 ` venom
2003-12-17 12:56 ` J.A. Magallon
2003-12-18 0:04 ` J.A. Magallon
2003-12-18 18:16 ` Martin Schlemmer
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=20031217113742.GC2074@werewolf.able.es \
--to=jamagallon@able.es \
--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