On 03/24/2010 07:34 AM, Ian Lance Taylor wrote:
trisha yad<trisha1march@xxxxxxxxx> writes:
When iam compiling test program if i don't use "-fno-optimize-sibling-calls" it
won't generate T.<num> symbols ,but in case of Kernel build even though
i won't use "-fno-optimize-sibling-calls" it is generating T.<num>.
Your problem is caused by bugs in the Linux kernel build system. At one
point someone thought the presence of these symbols indicated a bug in
the kernel source code, and the build scripts explicitly looked for them
and flagged them. With more recent kernels, it was realized that this
flagging is improper and it was removed.
I would suggest that you fix you fix your kernel build scripts rather
than trying to work around their faulty behavior.
Is there any way to prevent gcc(gcc4.4.1) from generating T.<num> in
case kernel build ?
I don't know what T.<num> symbols are.
I had this issue at one point. I forget what causes these symbols to be
emitted, but I do know that it is normal and not a compiler bug.
David Daney
