[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date: Tue, 10 Oct 2006 13:03:56 -0700
From: Jeremy Fitzhardinge <jeremy@...p.org>
To: Steven Rostedt <rostedt@...dmis.org>
CC: tim.c.chen@...ux.intel.com, Andrew Morton <akpm@...l.org>,
herbert@...dor.apana.org.au, linux-kernel@...r.kernel.org,
leonid.i.ananiev@...el.com
Subject: Re: [PATCH] Fix WARN_ON / WARN_ON_ONCE regression
Steven Rostedt wrote:
> Holy crap! I wonder where else in the kernel gcc is doing this. (of
> course I'm using gcc4 so I don't know). Is there another gcc attribute
> to actually tell gcc that a variable is really mostly read only (besides
> placing it in a mostly read only elf section)?
>
That would be nice, but I don't know of one (apart from "volatile",
which has its own downsides). Once could imagine an annotation which
makes gcc consider writes to the variable relatively expensive, so that
it avoids generating unnecessary/excessive writes.
J
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists