search for: gooseberry

...liasAnalysis::aliasGEP regarding "protecting TBAA in the case of > > dynamic indices into arrays of unions"; are you referring to that? > > Yes. And looking at the testcase, this appears to be the problem. > > Dan > > -- Not sent from my Blackberry, Raspberry or Gooseberry! -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20120206/c5c07f0c/attachment.html>

...ng this is a > mild hack used to work around the fact that the TBAA implementation > can't easily do the right thing for C code in the real world. > Possibly this is causing the loss of precision you're seeing. > > Dan > > -- Not sent from my Blackberry, Raspberry or Gooseberry! -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20120128/001fb5c9/attachment.html>

...around the fact that the TBAA implementation >> can't easily do the right thing for C code in the real world. >> Possibly this is causing the loss of precision you're seeing. >> >> Dan >> >> > > > -- > Not sent from my Blackberry, Raspberry or Gooseberry! > -- Not sent from my Blackberry, Raspberry or Gooseberry! -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20120130/7fd42aee/attachment.html>

On Fri, 2012-01-27 at 16:46 -0800, Dan Gohman wrote: > On Jan 27, 2012, at 4:15 PM, Maurice Marks wrote: > > > Our application generates IR that is used to generate X86_64 code for a Jit. We noticed that code generated with llvm 3.0 is worse in some circumstances that it was with 2.9. I traced the differences to alias analysis differences. Our IR references data structures that have

On Sat, Dec 11, 2010 at 4:19 PM, Maurice Marks <maurice.marks at gmail.com> wrote: > In my llvm jit project I needed to lookup BB addresses at execution time and > then jump to the corresponding BB. A C++ routine called at runtime from IR > finds the right BB, gets its BlockAddress and returns it as an i8*. The IR > does an indirectbr on this value... > Well, not really. The

On Jan 30, 2012, at 4:04 PM, Hal Finkel wrote: > > Dan, where in the code is this done? I see a comment at the end of > BasicAliasAnalysis::aliasGEP regarding "protecting TBAA in the case of > dynamic indices into arrays of unions"; are you referring to that? Yes. And looking at the testcase, this appears to be the problem. Dan

In my llvm jit project I needed to lookup BB addresses at execution time and then jump to the corresponding BB. A C++ routine called at runtime from IR finds the right BB, gets its BlockAddress and returns it as an i8*. The IR does an indirectbr on this value... Well, not really. The routine returns the address of a BlockAddress node. Is there any way to get the real runtime code address for the

...t; > http://lists.cs.uiuc.edu/pipermail/llvm-commits/Week-of-Mon-20110606/121937.html > > It would be really nice if you could post the result to the list :-) > > > regards > > /maurice marks > > Cheers, > Rafael > -- Not sent from my Blackberry, Raspberry or Gooseberry! -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20120224/0f96dc7c/attachment.html>

On Jan 27, 2012, at 4:15 PM, Maurice Marks wrote: > Our application generates IR that is used to generate X86_64 code for a Jit. We noticed that code generated with llvm 3.0 is worse in some circumstances that it was with 2.9. I traced the differences to alias analysis differences. Our IR references data structures that have lots of derived pointers and we use extensive tbaa metadata to

Our application generates IR that is used to generate X86_64 code for a Jit. We noticed that code generated with llvm 3.0 is worse in some circumstances that it was with 2.9. I traced the differences to alias analysis differences. Our IR references data structures that have lots of derived pointers and we use extensive tbaa metadata to indicate which pointers dont alias. Some of this seemed to be

Mi Maurice, A follow up to Andy's comments: MCJIT can find line numbers for ELF files, at least in limited circumstances. I know because I broke the regression test for it while doing some cleanup recently. ;) Looking at lib/ExecutionEngine/OProfileJIT/OProfileJITEventListener.cpp, I see the line: // TODO: support line number info (similar to IntelJITEventListener.cpp) >From a glance at