search for: metatadat

...(I prefer > the first.) Yes, this is very convenient. This along with the rest of Chris' proposal is very similar to the way we handled 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 t...

I've got a suggestion for a refinement: Right now, we have classes like DILocation that wrap an MDNode* to provide more convenient access to it. It would be more convenient for users if instead of MDNode *DbgInfo = Inst->getMD(MDKind::DbgTag); Inst2->setMD(MDKind::DbgTag, DbgInfo); they could write: DILocation DbgInfo = Inst->getMD<DILocation>();

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