Don't try to be smarter than the compiler about inlining
authorWouter Verhelst <w@uter.be>
Fri, 25 Jul 2014 07:46:19 +0000 (09:46 +0200)
committerWouter Verhelst <w@uter.be>
Fri, 25 Jul 2014 07:46:19 +0000 (09:46 +0200)
commit25933b1ac2e52db8e2df5b324bfc743b4dcbecc0
tree9e8bb5bf2e0bbf98b8f968baf2c84a8cf05317ec
parent3c13a8f984c6867dc17b68eceea7e0e7d611d2c7
Don't try to be smarter than the compiler about inlining

When we specify "inline int foo()" (as opposed to "static inline", I
guess), compilation may fail when compiling with -O0, as I sometimes do
to simplify debugging.

The compiler is way smarter about deciding when things are best inlined,
anyway. So stop trying to tell it what to do.
tests/code/dup.c