Re: [patch] i386: use C code for current_thread_info()

[Emmanuel Fleury]

Chuck Ebbert wrote:
> 
> I just tried gcc 3.3.3 and the kernel gets a little bigger but it boots
> and runs OK. That's the oldest compiler I can find.
> 
>    text    data     bss     dec     hex filename
> 3593627  559864  342728 4496219  449b5b 2.6.17-rc6-32-post/vmlinux
> 3591371  559864  342728 4493963  44928b 2.6.17-rc6-32/vmlinux
>   +2256
> 
> Looking at the generated code, it seems the compiler just makes dumb
> choices and tends to recompute current_thread_info() in unlikely code
> paths even when there is no register pressure.  4.0.2 makes better
> choices.

What size with gcc 4.1.2 ? (just curiosity)

Regards
-- 
Emmanuel Fleury              | Office: 211
Associate Professor,         | Phone: +33 (0)5 40 00 35 24
LaBRI, Domaine Universitaire | Fax:   +33 (0)5 40 00 66 69
351, Cours de la Libération  | email: fleury@xxxxxxxx
33405 Talence Cedex, France  | URL: http://www.labri.fr/~fleury
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/