search for: extensiblemetadata

Devang's work on debug info prompted this, thoughts welcome: http://nondot.org/sabre/LLVMNotes/ExtensibleMetadata.txt -Chris

On Sep 11, 2009, at 9:57 AM, Chris Lattner wrote: > Devang's work on debug info prompted this, thoughts welcome: > http://nondot.org/sabre/LLVMNotes/ExtensibleMetadata.txt The document mentions "instructions" a lot. We'll want to be able to apply metadata to ConstantExprs as well at least, if not also Arguments (think noalias) and other stuff, so it seems best to just talk about "values" instead, and DenseMap<Value *, ...> instead o...

Dan Gohman wrote: > On Sep 11, 2009, at 9:57 AM, Chris Lattner wrote: > > >> Devang's work on debug info prompted this, thoughts welcome: >> http://nondot.org/sabre/LLVMNotes/ExtensibleMetadata.txt > > The document mentions "instructions" a lot. We'll want to be able to > apply metadata to ConstantExprs as well at least, if not also Arguments > (think noalias) and other stuff, so it seems best to just talk about > "values" instead, and DenseMap<V...

On Sep 11, 2009, at 7:17 PM, Nick Lewycky wrote: > Dan Gohman wrote: >> On Sep 11, 2009, at 9:57 AM, Chris Lattner wrote: >>> Devang's work on debug info prompted this, thoughts welcome: >>> http://nondot.org/sabre/LLVMNotes/ExtensibleMetadata.txt >> The document mentions "instructions" a lot. We'll want to be able to >> apply metadata to ConstantExprs as well at least, if not also >> Arguments >> (think noalias) and other stuff, so it seems best to just talk about >> "values" inste...

...ner wrote: > > On Sep 11, 2009, at 7:17 PM, Nick Lewycky wrote: > >> Dan Gohman wrote: >>> On Sep 11, 2009, at 9:57 AM, Chris Lattner wrote: >>>> Devang's work on debug info prompted this, thoughts welcome: >>>> http://nondot.org/sabre/LLVMNotes/ExtensibleMetadata.txt >>> The document mentions "instructions" a lot. We'll want to be able to >>> apply metadata to ConstantExprs as well at least, if not also Arguments >>> (think noalias) and other stuff, so it seems best to just talk about >>> "values"...

Is there some documentation about metadata and how to use it somewhere? The doxygen-generated stuff obviously doesn't specify things like how to create custom metadata kinds and all that jazz. As a few of us discussed at the latest dev meeting, I'd like to use custom metadata to annotate load/store instructions with "nontemporal" semantics to allow generation of instructions

...eate custom metadata kinds and all that jazz. The metadata design and APIs are still evolving. I wouldn't recommend building anything on it just yet, but I'm hoping it will finalize and stabilize this month. The high-level idea and proposal was here: http://nondot.org/sabre/LLVMNotes/ExtensibleMetadata.txt > As a few of us discussed at the latest dev meeting, I'd like to use > custom metadata to annotate load/store instructions with "nontemporal" > semantics to allow generation of instructions like MOVNT on x86-based > targets. Losing the "nontemporal" annota...

...kinds and all that jazz. > > The metadata design and APIs are still evolving. I wouldn't recommend > building anything on it just yet, but I'm hoping it will finalize and > stabilize this month. The high-level idea and proposal was here: > http://nondot.org/sabre/LLVMNotes/ExtensibleMetadata.txt Cool. Is the goal to have it ready for 2.7? The nontemporal stuff is a rather large cause of merge conflicts for us and it would be nice to get it into the public repository before 2.7 is out. -Dave

On Fri, Sep 11, 2009 at 9:57 AM, Chris Lattner <clattner at apple.com> wrote: > Devang's work on debug info prompted this, thoughts welcome: > http://nondot.org/sabre/LLVMNotes/ExtensibleMetadata.txt Here is partial initial implementation. Thoughts ? - Devang -------------- next part -------------- A non-text attachment was scrubbed... Name: mdn.diff Type: application/octet-stream Size: 7860 bytes Desc: not available URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20090915/3b...

On Sep 11, 2009, at 2:11 PM, Dan Gohman wrote: > > On Sep 11, 2009, at 9:57 AM, Chris Lattner wrote: > > >> Devang's work on debug info prompted this, thoughts welcome: >> http://nondot.org/sabre/LLVMNotes/ExtensibleMetadata.txt > > The document mentions "instructions" a lot. We'll want to be able to > apply metadata to ConstantExprs as well at least, if not also > Arguments > (think noalias) and other stuff, so it seems best to just talk about > "values" instead, and DenseMa...

On Tue, Sep 15, 2009 at 11:37 PM, Devang Patel <devang.patel at gmail.com> wrote: > On Fri, Sep 11, 2009 at 9:57 AM, Chris Lattner <clattner at apple.com> wrote: >> Devang's work on debug info prompted this, thoughts welcome: >> http://nondot.org/sabre/LLVMNotes/ExtensibleMetadata.txt > > Here is partial initial implementation. > Thoughts ? setHasMetadata probably shouldn't be public, like there's no way to directly set HasValueHandle. I'd make the MDKindId type (or typedef) now so it's obvious what those "unsigned"s mean. Should the met...

...ame->ID, so the fact that StaticTypeId changes its values between runs isn't a problem. Thoughts? On Fri, Sep 11, 2009 at 9:57 AM, Chris Lattner <clattner at apple.com> wrote: > Devang's work on debug info prompted this, thoughts welcome: > http://nondot.org/sabre/LLVMNotes/ExtensibleMetadata.txt > > -Chris > _______________________________________________ > LLVM Developers mailing list > LLVMdev at cs.uiuc.edu         http://llvm.cs.uiuc.edu > http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev >

...at 2:11 PM, Dan Gohman wrote: > > >> >> >> On Sep 11, 2009, at 9:57 AM, Chris Lattner wrote: >> >> >> >> >> >>> Devang's work on debug info prompted this, thoughts welcome: >>> >>> http://nondot.org/sabre/LLVMNotes/ExtensibleMetadata.txt >>> >> >> >> The document mentions "instructions" a lot. We'll want to be able to >> >> apply metadata to ConstantExprs as well at least, if not also >> Arguments >> >> (think noalias) and other stuff, so it seems best to...

Talin wrote: > For example, the GWT compiler does type strengthening - that is, if you > are calling a method on an interface or abstract type, and the compiler > determines through live variable analysis what the concrete type is, > then it goes ahead and re-writes the type information to be the stronger > type. The advantage is that it may then be able to do additional >

Has anyone done any experiments with regards to type strengthening or weakening in the context of LLVM? For example, the GWT compiler does type strengthening - that is, if you are calling a method on an interface or abstract type, and the compiler determines through live variable analysis what the concrete type is, then it goes ahead and re-writes the type information to be the stronger