From: "David S. Miller" <davem@redhat.com>
To: dipankar@in.ibm.com
Cc: rusty@rustcorp.com.au, linux-kernel@vger.kernel.org,
torvalds@transmeta.com, davej@suse.de, andrea@suse.de,
paul.mckenney@us.ibm.com
Subject: Re: [BKPATCH] Read-Copy Update 2.5
Date: Mon, 26 Aug 2002 23:11:57 -0700 (PDT) [thread overview]
Message-ID: <20020826.231157.10296323.davem@redhat.com> (raw)
In-Reply-To: <20020827114152.A2072@in.ibm.com>
From: Dipankar Sarma <dipankar@in.ibm.com>
Date: Tue, 27 Aug 2002 11:41:52 +0530
On Tue, Aug 27, 2002 at 10:24:30AM +1000, Rusty Russell wrote:
> > +#ifdef CONFIG_PREEMPT
> > +/* Fake initialization to work around compiler breakage */
> > +DEFINE_PER_CPU(atomic_t[2], rcu_preempt_cntr) =
> > + {ATOMIC_INIT(0), ATOMIC_INIT(0)};
> > +DEFINE_PER_CPU(atomic_t, *curr_preempt_cntr) = NULL;
> > +DEFINE_PER_CPU(atomic_t, *next_preempt_cntr) = NULL;
>
> Also static I assume?
So, only statics are broken by gcc 2.95, right ?
I think it gets both static and non-static wrong.
Why don't we just specify that DEFINE_PER_CPU()'s must
have explicit initializers then we never need to think
about this ever again.
next prev parent reply other threads:[~2002-08-27 6:13 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-26 20:52 [BKPATCH] Read-Copy Update 2.5 Dipankar Sarma
2002-08-27 0:24 ` Rusty Russell
2002-08-27 6:11 ` Dipankar Sarma
2002-08-27 6:11 ` David S. Miller [this message]
2002-08-27 6:23 ` readsw/writesw readsl/writesl Andre Hedrick
2002-08-27 6:43 ` David S. Miller
2002-08-27 6:55 ` Andre Hedrick
2002-08-27 7:30 ` David S. Miller
2002-08-27 6:46 ` Benjamin Herrenschmidt
2002-08-27 6:49 ` Benjamin Herrenschmidt
2002-08-27 17:25 ` Alan Cox
2002-08-27 21:31 ` David S. Miller
2002-08-27 13:58 ` [BKPATCH] Read-Copy Update 2.5 Dipankar Sarma
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=20020826.231157.10296323.davem@redhat.com \
--to=davem@redhat.com \
--cc=andrea@suse.de \
--cc=davej@suse.de \
--cc=dipankar@in.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=paul.mckenney@us.ibm.com \
--cc=rusty@rustcorp.com.au \
--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 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.