On Mon, 5 Aug 2013 15:16:39 -0700 Andi Kleen <[email protected]> wrote:
> We cannot assume that the inline assembler code always ends up
> in the same file as the original C file.
um, why not? You put an asm(".text\n...") into a .c file and you
expect that assembly code to be emitted into the .s file then assembled
into the .o file.
Obviously something somewhere is doing something unexpected. Much more
detail needed, please.
Also... what's "lto"? Link Time Optimization? It's unclear how this
fits into that. Please provide that additional background info in these
patches so that others know what's going on and so that others (such as
me) can help people avoid making these mistakes in the future.
--
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/
