From: Dave Jones <davej@suse.de>
To: Anton Altaparmakov <aia21@cantab.net>
Cc: Linus Torvalds <torvalds@transmeta.com>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [2.5.9 patch] Fix bluesmoke/mce compiler warnings.
Date: Fri, 19 Apr 2002 16:35:59 +0200 [thread overview]
Message-ID: <20020419163558.G15517@suse.de> (raw)
In-Reply-To: <E16yVSw-0001Iv-00@storm.christs.cam.ac.uk> <E16yVSw-0001Iv-00@storm.christs.cam.ac.uk> <20020419150048.E15517@suse.de> <5.1.0.14.2.20020419150509.00a8c580@pop.cus.cam.ac.uk>
On Fri, Apr 19, 2002 at 03:16:32PM +0100, Anton Altaparmakov wrote:
> If gcc optimizes the "cpu" into a register then fine but if not, it would
> be IMHO preferable to use this instead:
>
> BUG_ON(*(unsigned int *)info != smp_processor_id());
I favoured simplicity over optimisation here, as it's not a speed critical path.
> >(This contains some other bits too that I intend to push to Linus after
> > a pre1 appears)
> Why not push now considering 2.5.9 isn't out yet?
I've not pulled Linus' bk tree, but have noticed from the changelogs
that some changes went in already touching this file.
> Considering the current bitkeeper tree on bkbits does not compile on ia32
> UP at all by any close margin, the more fixes that go in now the better...
Erk.
> Releasing 2.5.9 in current state would not be too useful for people like me
> who experience the ide problems...
Agreed. I assumed the Linus just didn't add the "pre1" part to EXTRAVERSION
yet but, given that 2.5.8 doesn't compile for a lot of people, I can see
why pushing 2.5.9 out sooner would be a good thing.
I've been busy with x86-64 bits and other projects the last few days, I'll
continue pushing more bits from my tree (including the bluesmoke bits) to
Linus over the weekend.
Dave.
--
| Dave Jones. http://www.codemonkey.org.uk
| SuSE Labs
prev parent reply other threads:[~2002-04-19 14:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-19 10:18 [2.5.9 patch] Fix bluesmoke/mce compiler warnings Anton Altaparmakov
2002-04-19 13:00 ` Dave Jones
2002-04-19 14:16 ` Anton Altaparmakov
2002-04-19 14:35 ` Dave Jones [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=20020419163558.G15517@suse.de \
--to=davej@suse.de \
--cc=aia21@cantab.net \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox