search for: statictypeid

...e"); to register a new kind. (I prefer the first.) These kind wrappers need a couple methods to make them work: const StringRef KindWrapper::name("..."); KindWrapper(MDNode*); // Except for special cases like LdStAlign. KindWrapper::operator bool() {return mdnode!=NULL;} // ?? int StaticTypeId<KindWrapper>::value; // Used for the proposal's MDKind KindWrapper::ValidOnValue(const Value*); MDNode* KindWrapper::merge(MDNode*, MDNode*) // For the optimizers StaticTypeId is a new class that maps each of its template arguments to a small, unique integer, which may be different in...

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

On Fri, Sep 11, 2009 at 3:23 PM, David Greene <dag at cray.com> wrote: > On Friday 11 September 2009 15:20, Jeffrey Yasskin wrote: >> StaticTypeId is a new class that maps each of its template arguments >> to a small, unique integer, which may be different in different >> executions. > > How does this work across compilation units?  How about with shared LLVM > libraries?  These kinds of global unique IDs are notoriously...

...ed metadata in a compiler I worked on years ago. It was so useful we even used it to stash dataflow information away as we did analysis. Of course we had metatadat tagged on control structures as well. I'd like to see the currently proposal extended to other constructs as Chris notes. > StaticTypeId is a new class that maps each of its template arguments > to a small, unique integer, which may be different in different > executions. How does this work across compilation units? How about with shared LLVM libraries? These kinds of global unique IDs are notoriously difficult to get righ...