[LLVMdev] typedef struct
Alvin Cheung
alvin.cheung at gmail.com
Sun Oct 4 09:41:20 PDT 2009
Hi Duncan,
Actually what I am doing is matching up each Type with its corresponding debug
info. I have checked that the debug info generated is consistent (i.e., typeA
is recorded as a derived type from composite type typeB in my example), but I
have seen cases where the name recorded in the Type object is typeA and
sometimes typeB, that's why I am confused.
Alvin
Duncan Sands wrote:
> Hi Alvin,
>
>> If I have a C struct declaration like this:
>>
>> typedef struct typeA {...} typeB;
>>
>> In the type symbol table generated should it contain an entry for
>> struct.typeA or struct.typeB? I seem to have seen both cases using
>> the same llvm toolchain so I just wonder if I have done something wrong.
>
> it doesn't matter what the name is since it has no effect on generated
> code. It's only in debug info that type names matter, so if you are not
> seeing this in debug info I wouldn't worry about it if I were you.
>
> Ciao,
>
> Duncan.
More information about the llvm-dev
mailing list