similar to: [LLVMdev] Inserting comments

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

On Tue, Nov 4, 2008 at 9:39 AM, Devang Patel <dpatel at apple.com> wrote: > >> 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? >> ... > > Try using llvm.var.annotation intrinsic. Thanks for the suggestion. I'd tried doing that by

On Mon, Nov 8, 2010 at 9:56 AM, Devang Patel <dpatel at apple.com> wrote: > > On Nov 6, 2010, at 7:35 PM, Talin wrote: > > After to speaking to Devang and a number of other people at the developer's > conference, I was able to make some forward progress on getting debugging to > work. I'm now able to actually single-step through my program and set > breakpoints,

To avoid going too off-topic on the multidimensional gep thread, I'm asking this in a separate thread. >> I took a look earlier and didn't notice any target-independent ones that would need a separate type parameter Do you know what would happen with the llvm.ptr.annotation intrinsic? Frontends use that to annotate members of structs: struct S { [[some_annotation]] int

On Nov 6, 2010, at 7:35 PM, Talin wrote: > After to speaking to Devang and a number of other people at the developer's conference, I was able to make some forward progress on getting debugging to work. I'm now able to actually single-step through my program and set breakpoints, and examine function parameters. > > However, I'm also seeing a lot of new problems which

After to speaking to Devang and a number of other people at the developer's conference, I was able to make some forward progress on getting debugging to work. I'm now able to actually single-step through my program and set breakpoints, and examine function parameters. However, I'm also seeing a lot of new problems which weren't exposed before. After spending the better part of two

On Dec 6, 2011, at 4:13 PM, Devang Patel wrote: > Hi Josh, > > On Dec 4, 2011, at 9:33 PM, Josh Matthews wrote: > >> I'm working on generating debug information for Rust, and I'm >> currently stumped on how to generate DWARF output via LLVM that will >> correctly represent this (eg. when exiting from foo2(), I'd like to >> see "Value returns

On Nov 8, 2010, at 10:52 PM, Talin <viridia at gmail.com> wrote: > On Mon, Nov 8, 2010 at 9:56 AM, Devang Patel <dpatel at apple.com> wrote: > > On Nov 6, 2010, at 7:35 PM, Talin wrote: > >> After to speaking to Devang and a number of other people at the developer's conference, I was able to make some forward progress on getting debugging to work. I'm now

Hi All,   While collecting type information for "anonymous types", I had below observation.   For the example with anonymous types, given below struct test {   struct {     union {       Char a[4];     };   };   struct {     int b;     char c;   }; };   LLVM 2.6 defines the types as %struct.anon1 = type { %union.anon0} %struct.anon2 = type { i32, i8} %struct.test = type {

Hi, I'm interested in whether or not there is a way of providing source-level annotations to help LLVM with optimizations, similar to VisualC++'s __assume facility (http://msdn.microsoft.com/en-us/library/1b3fsfxw.aspx). As part of our PHP compiler (phpcompiler.org), it would be great to be able to annotate our generated C code with, for example, (var != NULL), or (var->type ==

Pankaj, I encourage you to read Chris's excellent blog entry on type system @ http://blog.llvm.org/2011/11/llvm-30-type-system-rewrite.html - Devang On Dec 6, 2011, at 3:54 AM, Pankaj Gode wrote: > Hi All, > > While collecting type information for "anonymous types", I had below observation. > > For the example with anonymous types, given below > struct test

On Tue, Nov 9, 2010 at 9:04 AM, Devang Patel <dpatel at apple.com> wrote: > > > On Nov 8, 2010, at 10:52 PM, Talin <viridia at gmail.com> wrote: > > On Mon, Nov 8, 2010 at 9:56 AM, Devang Patel < <dpatel at apple.com> > dpatel at apple.com> wrote: > >> >> On Nov 6, 2010, at 7:35 PM, Talin wrote: >> >> After to speaking to Devang

On Fri, Feb 10, 2012 at 1:14 PM, Devang Patel <dpatel at apple.com> wrote: > > On Feb 10, 2012, at 10:19 AM, Hal Finkel <hfinkel at anl.gov> wrote: > >> Is there currently a good way of attaching metadata to loops? >> >> The use case that I have in mind is implementing a feature whereby the >> user can put >> #pragma unroll(N) >> above a

On Fri, Feb 10, 2012 at 3:53 PM, Devang Patel <dpatel at apple.com> wrote: > How would you tie a built-in call with a loop ? The same way as Hal was saying: tag the loop header. Sebastian -- Qualcomm Innovation Center, Inc is a member of Code Aurora Forum

Unfortunately this is what I'm already doing, and it's not working. I drew inspiration from a disassembly of a program that showed that struct foo { int a; float b; char buf[80]; } struct foo get_foo(void) { foo f = { 5, 2.5 }; return f; } would turn into define void @get_foo(%struct.foo* sret %agg.result) nounwind ssp { ... call void @llvm.memcpy.p0i8.p0i8.i64(i8* %2, i8*

Is there currently a good way of attaching metadata to loops? The use case that I have in mind is implementing a feature whereby the user can put #pragma unroll(N) above a loop and that serves has an instruction to the optimizer to unroll the loop N times. I understand that LLVM does not have a first-class loop construct, but would attaching the metadata to the instructions that branch to the

Hi guys, a question about updating memory SSA: Is it expected that e.g insertion of MemoryDef doesn't change all dominated uses? For example test case CreateLoadsAndStoreUpdater produces: define void @F(i8*) { ; 1 = MemoryDef(liveOnEntry) store i8 16, i8* %0 ; 4 = MemoryDef(1) store i8 16, i8* %0 br i1 true, label %2, label %3 ; <label>:2: ;

Hey Devang, Thanks for the assist, I'm trying to extract a signature which uniquely identifies a block of code.... this is required for a project I am doing. The no of data structures is one of the identifying features of this signature. Thanks Nipun On Fri, Oct 31, 2008 at 1:05 PM, Devang Patel <dpatel at apple.com> wrote: > Hi Nipun, > On Oct 30, 2008, at 9:31 PM, Nipun

On 12/16/2016 11:37 AM, Michael Kuperstein wrote: > Calling an instruction a "source" is basically another way to say "we > can't dataflow through this". > > What I'm trying to say is that this is not really a property of the > instruction type. > I agree we should be adding annotations sparingly - that is, we should > not annotate something we

On Feb 10, 2012, at 10:19 AM, Hal Finkel <hfinkel at anl.gov> wrote: > Is there currently a good way of attaching metadata to loops? > > The use case that I have in mind is implementing a feature whereby the > user can put > #pragma unroll(N) > above a loop and that serves has an instruction to the optimizer to > unroll the loop N times. > > I understand that