Hi,
On 7/9/07, Ralf Baechle <[email protected]> wrote:
On Sat, Jul 07, 2007 at 03:03:30AM +0200, Adrian Bunk wrote:
> "extern inline" will have different semantics with gcc 4.3,
> and "static inline" is correct here.
The idea was to have a linker error in case gcc should deciede for some
reason not to inline this function which as I understand will continue
to be the behaviour of gcc 4.3?
I don't know for this peculiar case but it usually is a good thing to
let gcc decide if the function needs to be inlined or not.
If we really want this function to be inlined in all cases, maybe we
should use __always_inline attribute instead ?
--
Franck
-
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/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
