search for: p0struct

...ypeid.c There is a limitation of the newly introduced intrinsic that, I can't find a way to make the intrinsic to accept all types without name mangling. Therefore, we have to define different intrinsics for different type. See the example below, by using macro trick, we define llvm.typeid.for.p0struct.mystr and llvm.typeid.for.p0struct.mystr2, and also the different output functions. Another problem is that I'm still unable to find a way to insert dwarf information in this stage. After clang, debug information are already isolated, and debug information entries are linked together. Adjustin...

On 2015/8/12 12:57, Alexei Starovoitov wrote: > On Wed, Aug 12, 2015 at 10:34:43AM +0800, Wangnan (F) via llvm-dev wrote: >> Think about a program like this: >> >> struct strA { int a; } >> struct strB { int b; } >> int func() { >> struct strA a; >> struct strB b; >> >> a.a = 1; >> b.b = 2; >>