I am the colleague of OP.
Let me clarify few things which OP forgot to mention. ( Get a cup of
coffee, Trisha ! ) :
a) Our problem : As discussed, some of the function symbol names
appear as T.XXX in the symbol-section of Linux kernel ELF file.
The build is OK and there is no script-fail issue here ( as Mr
Daney seems to think. )
Our company wants us to fix this problem. We dont want to "remove"
these symbols. Instead , we want that these symbols should
appear with the original function-names which they represent.
For example, if there is a kernel-fault occurring near/after
T.XXX , we want the correct function-name to get displayed in
backtrace.
We cannot change the toolchain version. We need Cortex support.
Also , we dont think there is any connection to inlining here.
Looking at the objdump shows that T.XXX is a normal function which
gets called
with the usual bl call in ARM.
thanks
On Mon, Mar 29, 2010 at 11:09 PM, David Daney <ddaney@xxxxxxxxxxxxxxxxxx> wrote:
> On 03/26/2010 08:51 PM, trisha yad wrote:
>>
>> Hi all,
>>
>> Yes David if i build my kernel with GCC 4.3.3 there is no issue.
>> But since we have to use Cortex a9 support, which is in GCC 4.4 so
>> that is reason for using current tool chain.
>>
>> I also try to build Linux 2.6.33, and got the same problem.
>>
>
> Look at the error messages you are getting. Take the part of the message
> that doesn't contain a symbol name or other text that varies. Grep all the
> kernel sources for that text (especially the scripts directory). That
> should show you where the messages that are upsetting you are generated.
> Then do one of the following:
>
> 1) Delete the lines of the scripts that generate the message. After
> doing that you should be happy.
>
> 2) Share with us the exact location in the kernel sources the messages
> are generated.
>
> 2a) Someone might analyze the situation further and help you.
> 2b) Delete the lines of the scripts after being assured that they
> shouldn't be there. Now you should be happy.
>
>
>> I could not find a clue to get correct symbols.
>>
>> Kind regards
>> trisha
>>
>>
>> On Sat, Mar 27, 2010 at 12:08 AM, David Daney<ddaney@xxxxxxxxxxxxxxxxxx>
>> wrote:
>>>
>>> On 03/26/2010 10:27 AM, Ian Lance Taylor wrote:
>>>>
>>>> trisha yad<trisha1march@xxxxxxxxx> writes:
>>>>
>>>>> arm-linux-gnueabi-gcc -fno-optimize-sibling-calls -O2 test.c
>>>>> I can see Function name Convert to
>>>>> 0000842c t T.12
>>>>
>>>> You still haven't explained what is wrong with that symbol. Why does
>>>> it matter?
>>>
>>> I thought I already said this, but here it is again:
>>>
>>> Some broken Linux kernel build scripts flag the presence of these symbols
>>> a
>>> something very bad. If you try building a kernel containing these
>>> scripts,
>>> you might be lead to think that the end of the world is near.
>>>
>>> Obviously the way to fix the problem is to change GCC so it doesn't
>>> trigger
>>> the emission of these messages in the defective kernels. :-)
>>>
>>>
>>> David Daney
>>>
>>
>
>
