From: Richard Henderson <rth@twiddle.net>
To: Michal Moskal <malekith@pld.org.pl>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] gcc-3.1 ffs problem, kernel 2.4.18
Date: Thu, 28 Mar 2002 21:10:25 -0800 [thread overview]
Message-ID: <20020328211025.A30037@twiddle.net> (raw)
In-Reply-To: <20020320174238.GA13533@ep09.kernel.pl>
On Wed, Mar 20, 2002 at 06:42:38PM +0100, Michal Moskal wrote:
> Following patch is needed to compile linux-2.4.18 with xfs patch with
> recent gcc 3.1 snapshot.
What is the failure mode?
> It is clearly bug in linux includes (they use asm code unconditionally,
> even on constants, ...
So? I don't see that that's a *bug* at all. A missed optimization
opportunity yes, bug no.
> Beside this linux-2.4.18 compiled with gcc-3.1 20020311 works fine for
> me.
Thanks for testing though.
r~
next prev parent reply other threads:[~2002-03-29 5:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-20 17:42 [PATCH] gcc-3.1 ffs problem, kernel 2.4.18 Michal Moskal
2002-03-29 5:10 ` Richard Henderson [this message]
[not found] ` <20020329115731.GA3227@ep09.kernel.pl>
[not found] ` <20020329144232.A495@twiddle.net>
[not found] ` <20020402114848.GA9004@ep09.kernel.pl>
2002-04-02 22:59 ` Richard Henderson
2002-04-03 0:04 ` Linus Torvalds
2002-04-03 11:00 ` Richard Henderson
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=20020328211025.A30037@twiddle.net \
--to=rth@twiddle.net \
--cc=linux-kernel@vger.kernel.org \
--cc=malekith@pld.org.pl \
/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