search for: comment4852

Hi Anyone have any clever way of inserting a comment (or comment-ish-thing) that will make it to an .ll that's generated at the same time as writing out the bitcode? I'd been hacking comments in using an alloca with the name of the value being the comment, but just realized that they weren't getting removed at the codegen level despite being unused (no opt), when I got a stack

On Nov 4, 2008, at 12:57 AM, Scott Graham wrote: > Hi > > Anyone have any clever way of inserting a comment (or > comment-ish-thing) that will make it to an .ll that's generated at the > same time as writing out the bitcode? > > I'd been hacking comments in using an alloca with the name of the > value being the comment, but just realized that they weren't

...me time as writing out the bitcode? >> ... > > Try using llvm.var.annotation intrinsic. Thanks for the suggestion. I'd tried doing that by annotating a null, but then at each "comment" point I get: call void @llvm.var.annotation( i8* null, i8* getelementptr ([16 x i8]* @comment4852, i32 0, i32 0), i8* null, i32 0 ) Slightly useful, but then you have to hunt down the definition of "@comment4852" which isn't great. ... Oh, but llvm.annotation.* is workable (ignoring the unique-ing append of "14"): %"------- my comment here14" = call i8 @llv...