From: David Mosberger <davidm@hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] volatile unsigned long cpu_online_map vs unsigned long cpu_online_map
Date: Tue, 26 Jun 2001 16:12:26 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590693005771@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590693005770@msgid-missing>
>>>>> On 26 Jun 2001 17:34:52 +0200, Andreas Schwab <schwab@suse.de> said:
Andreas> include/asm-ia64/smp.h has 'extern unsigned long
Andreas> cpu_online_map', but arch/ia64/kernel/setup.c and
Andreas> arch/ia64/kernel/smpboot.c have 'volatile unsigned long
Andreas> cpu_online_map'. Which one is correct?
It should be volatile. Apparently, there were some changes in the
gcc3.0 tree shortly before the final release which made gcc more picky
(at least I don't recall seeing those messages before). Also, I think
there may be a new code generation problem in gcc3.0: the kernel gets
stuck in the middle of the boot (after the message "Starting up
secondaries"). I'll try to look into this soon, but I'm at Usenix the
rest of this week and on vacation right afterwards, so I may not get
to it until mid-July. So it looks like gcc3.0 isn't as kernel-ready
as I thought it was. Bummer.
--david
prev parent reply other threads:[~2001-06-26 16:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-26 15:34 [Linux-ia64] volatile unsigned long cpu_online_map vs unsigned long cpu_online_map Andreas Schwab
2001-06-26 16:12 ` David Mosberger [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=marc-linux-ia64-105590693005771@msgid-missing \
--to=davidm@hpl.hp.com \
--cc=linux-ia64@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