search for: aspicere

...the remark in your mail of 09/04/2006 to Nikhil >> Patil about >> "-g currently disables many optimizations" still holds. > > Yes, that is true. What are you trying to do? Basically, I'm working on an aspect weaver (next version of http:// users.ugent.be/~badams/aspicere/) where the weaving functionality is performed at link-time by some LLVM passes I'm writing. As advice frequently needs join point-specific context information like the name of the woven advice, of the current method, of the current compilation unit, ... I provide this info by storing i...

On Mon, 25 Sep 2006, Bram Adams wrote: > Op 25-sep-06, om 20:07 heeft Chris Lattner het volgende geschreven: >> What are you trying to accomplish? Why not use location records from >> debug info? > > You mean the debugging intrinsics? Just discovered them :-), and I guess > that's exactly what I need. Haven't tried them extensively yet, so I'm >

Hi, Op 25-sep-06, om 20:07 heeft Chris Lattner het volgende geschreven: > What are you trying to accomplish? Why not use location records from > debug info? You mean the debugging intrinsics? Just discovered them :-), and I guess that's exactly what I need. Haven't tried them extensively yet, so I'm wondering whether the remark in your mail of 09/04/2006 to Nikhil Patil

...09/04/2006 to Nikhil >>> Patil about >>> "-g currently disables many optimizations" still holds. >> >> Yes, that is true. What are you trying to do? > > Basically, I'm working on an aspect weaver (next version of http:// > users.ugent.be/~badams/aspicere/) where the weaving functionality is > performed at link-time by some LLVM passes I'm writing. As advice ok. > frequently needs join point-specific context information like the > name of the woven advice, of the current method, of the current > compilation unit, ... I provide this...