From: Andrea Arcangeli <andrea@suse.de>
To: root <root@nospam.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.4.5pre2aa1 panic during boot
Date: Sun, 20 May 2001 19:30:43 +0200 [thread overview]
Message-ID: <20010520193043.B30738@athlon.random> (raw)
In-Reply-To: <3B07F7ED.7C22DAFD@nospam.com>
In-Reply-To: <3B07F7ED.7C22DAFD@nospam.com>; from root@nospam.com on Mon, May 21, 2001 at 01:59:25AM +0900
On Mon, May 21, 2001 at 01:59:25AM +0900, root wrote:
> Andrea told us that he will not care for anything
> compiled with gcc-2.95 or version lower than that.
I said I don't care about bugreport of alpha kernel crashes if the
_alpha_ kernel was compiled with gcc 2.95.*. 2.95 is fine on the x86,
but it's broken on the alpha. In short:
x86 2.4 kernels -> use 2.95.[34] or egcs 1.1.2 (I
use 2.95.4 from the
gcc_2_95_branch of CVS)
alpha 2.4 kernel -> use egcs 1.1.2 or 2.96 with some
houndred of patches (I
personally still use the egcs
1.1.2)
> However, it seems that this kernel panic has anything
> to do with gcc-2.95.
Please try to reproduce with egcs 1.1.2 to be sure.
> Anyway, gcc-2.95 is still the official release of gcc.
> Even SuSE-7.1 has this version only. I wish SuSE puts
x86 and alpha are completly different issues with regard to the
compiler. I never heard of problems with 2.95.4 on x86 and I would never
replace 2.95.4 from the gcc_2_95_branch for the latest 2.96 on my x86
boxes, I'd instead try again gcc 3.0 after the inline asm fixes for "+="
constranints on local variables are done.
Andrea
prev parent reply other threads:[~2001-05-20 17:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-20 16:59 2.4.5pre2aa1 panic during boot root
2001-05-20 17:30 ` Andrea Arcangeli [this message]
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=20010520193043.B30738@athlon.random \
--to=andrea@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=root@nospam.com \
/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.