linux-toradex.git/include/linux/compiler.h, branch v2.6.23.5

make __chk_{user,io}_ptr() accept pointers to volatile

2007-07-26T18:11:57+00:00

Signed-off-by: Al Viro 
Signed-off-by: Linus Torvalds

x86: Support attribute((cold)) in gcc 4.3

2007-07-22T01:37:08+00:00

gcc 4.3 supports a new __attribute__((__cold__)) to mark functions cold. Any
path directly leading to a call of this function will be unlikely. And gcc
will try to generate smaller code for the function itself.

Please use with care. The code generation advantage isn't large and in most
cases it is not worth uglifying code with this.

This patch marks some common error functions like panic(), printk()
as cold.  This will longer term make many unlikely()s unnecessary, although
we can keep them for now for older compilers.

BUG is not marked cold because there is currently no way to tell
gcc to mark a inline function told.

Also all __init and __exit functions are marked cold. With a non -Os
build this will tell the compiler to generate slightly smaller code
for them. I think it currently only uses less alignments for labels,
but that might change in the future.

One disadvantage over *likely() is that they cannot be easily instrumented
to verify them.

Another drawback is that only the latest gcc 4.3 snapshots support this.
Unfortunately we cannot detect this using the preprocessor. This means older
snapshots will fail now. I don't think that's a problem because they are
unreleased compilers that nobody should be using.

gcc also has a __hot__ attribute, but I don't see any sense in using
this in the kernel right now. But someday I hope gcc will be able
to use more aggressive optimizing for hot functions even in -Os,
if that happens it should be added.

Includes compile fix from Thomas Gleixner.

Cc: Jan Hubicka 
Signed-off-by: Andi Kleen 
Signed-off-by: Linus Torvalds

x86_64: Support gcc 5 properly

2007-05-21T16:56:57+00:00

The ifdef tests were broken.  Assume it acts like gcc 4

Signed-off-by: Andi Kleen 
Signed-off-by: Linus Torvalds

compiler: introduce used and maybe_unused

2007-05-09T19:30:56+00:00

__used is defined to be __attribute__((unused)) for all pre-3.3 gcc
compilers to suppress warnings for unused functions because perhaps they
are referenced only in inline assembly.  It is defined to be
__attribute__((used)) for gcc 3.3 and later so that the code is still
emitted for such functions.

__maybe_unused is defined to be __attribute__((unused)) for both function
and variable use if it could possibly be unreferenced due to the evaluation
of preprocessor macros.  Function prototypes shall be marked with
__maybe_unused if the actual definition of the function is dependant on
preprocessor macros.

No update to compiler-intel.h is necessary because ICC supports both
__attribute__((used)) and __attribute__((unused)) as specified by the gcc
manual.

__attribute_used__ is deprecated and will be removed once all current
code is converted to using __used.

Cc: Rusty Russell 
Cc: Adrian Bunk 
Signed-off-by: David Rientjes 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds

[PATCH] Add const to pointer qualifiers for __chk_user_ptr and __chk_io_ptr.

2007-03-26T21:23:52+00:00

Change prototypes for __chk_user_ptr and __chk_io_ptr to take const
void* instead of void*, so that code can pass "const void *" to them.

(Right now sparse does not warn about passing const void* to void*
functions, but that is a separate bug that I believe Josh is working on,
and once sparse does check this, the changed prototypes will be
necessary.)

Signed-off-by: Russ Cox 
Signed-off-by: Josh Triplett 
Acked-by: Christopher Li 
Signed-off-by: Linus Torvalds

include/linux/compiler.h: reject gcc 3 < gcc 3.2

2006-12-12T18:28:50+00:00

The kernel doesn't compile with GCC <3.2, do not allow it to succeed if GCC
3.0.x or 3.1.x are used.

Signed-off-by: Alistair John Strachan 
Signed-off-by: Adrian Bunk

[PATCH] Pass sparse the lock expression given to lock annotations

2006-10-01T07:39:26+00:00

The lock annotation macros __acquires, __releases, __acquire, and __release
all currently throw away the lock expression passed as an argument.  Now
that sparse can parse __context__ and __attribute__((context)) with a
context expression, pass the lock expression down to sparse as the context
expression.  This requires a version of sparse from GIT commit
37475a6c1c3e66219e68d912d5eb833f4098fd72 or later.

Signed-off-by: Josh Triplett 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds

[PATCH] Pass a lock expression to __cond_lock, like acquire and release

2006-09-29T16:18:20+00:00

Currently, __acquire and __release take a lock expression, but __cond_lock
takes only a condition, not the lock acquired if the expression evaluates
to true.  Change __cond_lock to accept a lock expression, and change all
the callers to pass in a lock expression.

Signed-off-by: Josh Triplett 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds

add CONFIG_ENABLE_MUST_CHECK

2006-09-26T04:08:39+00:00

Those 1500 warnings can be a bit of a pain.  Add a config option to shut them
up.

Signed-off-by: Andrew Morton 
Signed-off-by: Greg Kroah-Hartman

Restore __attribute_const__ to user-visibility in linux/compiler.h...for now

2006-05-03T23:41:02+00:00

Signed-off-by: David Woodhouse