From: Andrew Beresford <beezly@beezly.org.uk>
To: "David S. Miller" <davem@redhat.com>
Cc: hch@infradead.org, linux-kernel@vger.kernel.org
Subject: Re: OOPS: ext3/sparc badness
Date: Tue, 21 May 2002 09:30:04 +0100 [thread overview]
Message-ID: <20020521083004.GB18501@monkey.beezly.org.uk> (raw)
In-Reply-To: <1021897921.8474.8.camel@montgomery> <20020520.143018.82222608.davem@redhat.com> <20020520225206.A15153@infradead.org> <20020520.150628.25332319.davem@redhat.com>
David,
On Mon, May 20, 2002 at 03:06:28PM -0700, David S. Miller wrote:
> From: Christoph Hellwig <hch@infradead.org>
> Date: Mon, 20 May 2002 22:52:06 +0100
>
> On Mon, May 20, 2002 at 02:30:18PM -0700, David S. Miller wrote:
> > Unsupported compiler for sparc64 kernels. Your OOPS report is going
> > to be ignored.
Understood, but the reason I was using 3.0.4 was because sparc64-egcs
has been suspected of generating some bad code in the md.c (see the link
in the previous e-mail I sent).
> Btw, is gcc 3.1 supported now or only the magic egcs variant?
>
> gcc-3.1 should work properly, I've used it but I'm hesitant to %100
> bless it just yet. :-)
>
> I would prefer to receive bug reports only against the sparc64-egcs
> compiler still.
I will give gcc-3.1 a try.
Cheers,
Beezly
next prev parent reply other threads:[~2002-05-21 8:30 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-20 12:32 Beezly
2002-05-20 14:55 ` Beezly
2002-05-20 21:30 ` David S. Miller
2002-05-20 21:52 ` Christoph Hellwig
2002-05-20 22:06 ` David S. Miller
2002-05-21 8:30 ` Andrew Beresford [this message]
2002-05-21 8:18 ` David S. Miller
2002-05-21 8:38 ` Andrew Beresford
2002-05-21 8:34 ` David S. Miller
2002-05-21 9:08 ` Andrew Beresford
2002-08-31 0:18 ` David S. Miller
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=20020521083004.GB18501@monkey.beezly.org.uk \
--to=beezly@beezly.org.uk \
--cc=davem@redhat.com \
--cc=hch@infradead.org \
--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®