On Thu, 3 May 2001, Albert D. Cahalan wrote: > Pavel Machek writes: > > > It should ot break anything. gcc decides its bad to inline it, so it > > does not inline it. Small code growth at worst. Compiler has right to > > make your code bigger or slower, if it decides to do so. > > Oh come on. The logical way: > > inline Compiler must inline (only!) or report an error. That's doable now.. if the code is otherwise warning free. -Mike - 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/
- iso9660 endianness cleanup patch H. Peter Anvin
- Re: iso9660 endianness cleanup patch Linus Torvalds
- Re: iso9660 endianness cleanup patch H. Peter Anvin
- Re: iso9660 endianness cleanup patch Pavel Machek
- Re: iso9660 endianness cleanup pat... Albert D. Cahalan
- Re: iso9660 endianness cleanu... Mike Galbraith
- Re: iso9660 endianness cleanup patch Albert D. Cahalan
- Re: iso9660 endianness cleanup patch Tim Riker
- Re: iso9660 endianness cleanup patch Martin Dalecki
- Re: iso9660 endianness cleanup patch H. Peter Anvin
- Re: iso9660 endianness cleanup patch Pavel Machek
- Re: iso9660 endianness cleanup patch Andrzej Krzysztofowicz
- Re: iso9660 endianness cleanup patch H. Peter Anvin
- Re: iso9660 endianness cleanup patch H. Peter Anvin
- Re: FIXED iso9660 endianness cleanup p... H. Peter Anvin
- Re: iso9660 endianness cleanup patch Alan Cox