search for: createtbaanode

Displaying 4 results from an estimated 4 matches for "createtbaanode".

2013 Oct 08
2
[LLVMdev] dragonegg: switch from old TBAA format to the new struct-path aware TBAA format
Hi Duncan, I am hoping to remove the support for the old TBAA format soon. You should be able to switch to the new format by replacing MDNode *AliasTag = MDHelper.createTBAANode(TreeName, getTBAARoot()); with MDNode *AliasType = MDHelper.createTBAAScalarTypeNode(TreeName, getTBAARoot()); MDNode *AliasTag = MDHelper.createTBAAStructTagNode(AliasType, AliasType, 0) Also replacing LeafTag->replaceAllUsesWith(getTBAARoot()); with MDNode *Root = getTBAARoot(); LeafTag-&gt...
2013 Oct 12
0
[LLVMdev] dragonegg: switch from old TBAA format to the new struct-path aware TBAA format
...Is the offset field really useful/necessary? Best wishes, Duncan. On 08/10/13 02:47, Manman Ren wrote: > Hi Duncan, > > I am hoping to remove the support for the old TBAA format soon. > You should be able to switch to the new format by replacing > > MDNode *AliasTag = MDHelper.createTBAANode(TreeName, getTBAARoot()); > > with > MDNode *AliasType = MDHelper.createTBAAScalarTypeNode(TreeName, getTBAARoot()); > MDNode *AliasTag = MDHelper.createTBAAStructTagNode(AliasType, AliasType, 0) > > Also replacing > LeafTag->replaceAllUsesWith(getTBAARoot()); > > with...
2015 May 28
0
[LLVMdev] Naming TBAA nodes in LLVM >=3.6?
In Julia's use of LLVM, we were naming TBAA nodes with logic like this for LLVM 3.3: static MDNode *tbaa_make_child( const char *name, MDNode *parent, bool isConstant=false ) { MDNode *n = mbuilder->createTBAANode(name,parent,isConstant); n->setValueName( ValueName::Create(name, name+strlen(name))); return n; } The names would show up in dumps of the IR (e.g. "call F.dump()" from gdb) , which was really handy for debugging. But with LLVM 3.6's split of Value and MDNode, the naming...
2016 Nov 01
2
Ambiguity in !tbaa metadata?
I was trying to add some stronger assertions in the verifier around !tbaa metadata when I ran into an ambiguity: I think the encoding of the metadata nodes are such that a given node can be interpreted as either a struct type node or a scalar tbaa node. I'd like a sanity check before I try to fix or work around this. Consider some IR that I got from running clang over a small C++ program: