> > Eh, not really. "__inline__" is GCC-specific and probably won't work in other > compilers (unless you did "#define __inline__", which would bloat the code a > lot). > But ___inline is a C99 keyword, isnot it? Jan Engelhardt -- - 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/
- Follow-Ups:
- Re: [RFC][PATCH 0/2] KABI example conversion and cleanup
- From: Ben Pfaff <[email protected]>
- [OT] Non-GCC compilers used for linux userspace
- From: Kyle Moffett <[email protected]>
- Re: [RFC][PATCH 0/2] KABI example conversion and cleanup
- References:
- [ANNOUNCE] linux-libc-headers dead
- From: Mariusz Mazur <[email protected]>
- [RFC][PATCH 0/2] KABI example conversion and cleanup
- From: Kyle Moffett <[email protected]>
- Re: [RFC][PATCH 0/2] KABI example conversion and cleanup
- From: Eric Piel <[email protected]>
- Re: [RFC][PATCH 0/2] KABI example conversion and cleanup
- From: Rob Landley <[email protected]>
- Re: [RFC][PATCH 0/2] KABI example conversion and cleanup
- From: Eric Piel <[email protected]>
- Re: [RFC][PATCH 0/2] KABI example conversion and cleanup
- From: Kyle Moffett <[email protected]>
- [ANNOUNCE] linux-libc-headers dead
- Prev by Date: RE: HZ != 1000 causes problem with serial device shown by git-bisect
- Next by Date: Re: 2.6.16: Oops - null ptr in blk_recount_segments?
- Previous by thread: Re: [RFC][PATCH 0/2] KABI example conversion and cleanup
- Next by thread: [OT] Non-GCC compilers used for linux userspace
- Index(es):
 |