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 [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
- References:
- [PATCH] Fix WARN_ON / WARN_ON_ONCE regression
- From: Tim Chen <[email protected]>
- Re: [PATCH] Fix WARN_ON / WARN_ON_ONCE regression
- From: Jeremy Fitzhardinge <[email protected]>
- Re: [PATCH] Fix WARN_ON / WARN_ON_ONCE regression
- From: Tim Chen <[email protected]>
- Re: [PATCH] Fix WARN_ON / WARN_ON_ONCE regression
- From: Jeremy Fitzhardinge <[email protected]>
- Re: [PATCH] Fix WARN_ON / WARN_ON_ONCE regression
- From: Tim Chen <[email protected]>
- Re: [PATCH] Fix WARN_ON / WARN_ON_ONCE regression
- From: Andrew Morton <[email protected]>
- Re: [PATCH] Fix WARN_ON / WARN_ON_ONCE regression
- From: Tim Chen <[email protected]>
- Re: [PATCH] Fix WARN_ON / WARN_ON_ONCE regression
- From: Andrew Morton <[email protected]>
- Re: [PATCH] Fix WARN_ON / WARN_ON_ONCE regression
- From: Tim Chen <[email protected]>
- Re: [PATCH] Fix WARN_ON / WARN_ON_ONCE regression
- From: Steven Rostedt <[email protected]>
- [PATCH] Fix WARN_ON / WARN_ON_ONCE regression
- Prev by Date: Re: 2.6.18 suspend regression on Intel Macs
- Next by Date: RE: Hugepage regression
- Previous by thread: Re: [PATCH] Fix WARN_ON / WARN_ON_ONCE regression
- Next by thread: Re: [PATCH] Fix WARN_ON / WARN_ON_ONCE regression
- Index(es):
 |