search for: opderef

Seems the last use of DIFactory in LLVM/Clang is in: clang/lib/CodeGen/CGDebugInfo.cpp to get the enums llvm::DIFactory::OpDeref and llvm::DIFactory::OpPlus. Shouldn't this be moved to DIBuilder and remove the dependency completely? -- cheers, --renato http://systemcall.org/ Reclaim your digital rights, eliminate DRM, learn more at http://www.defectivebydesign.org/what_is_drm

...can we not follow the naming conventions in the developer guidelines? On Fri, Feb 18, 2011 at 5:14 AM, Renato Golin <rengolin at systemcall.org>wrote: > Seems the last use of DIFactory in LLVM/Clang is in: > > clang/lib/CodeGen/CGDebugInfo.cpp to get the enums > llvm::DIFactory::OpDeref and llvm::DIFactory::OpPlus. > > Shouldn't this be moved to DIBuilder and remove the dependency completely? > > -- > cheers, > --renato > > http://systemcall.org/ > > Reclaim your digital rights, eliminate DRM, learn more at > http://www.defectivebydesign.org/wh...

...ing through DIBuilder::insertDeclare(): What kind of instructions are supported as the "storage" parameter? Is it only allocas? I've also had some success with a combination of llvm::Argument and DIBuilder::createComplexVariable(). That is, create a DIVariable with one additional OpDeref and then use DIBuilder::insertDeclare(argument, variable_info, basic_block). Is this kind of usage supported or do I always have to use allocas to make this work reliably? Thanks in advance, Michael

...conventions in the developer guidelines? > > On Fri, Feb 18, 2011 at 5:14 AM, Renato Golin <rengolin at systemcall.org>wrote: > >> Seems the last use of DIFactory in LLVM/Clang is in: >> >> clang/lib/CodeGen/CGDebugInfo.cpp to get the enums >> llvm::DIFactory::OpDeref and llvm::DIFactory::OpPlus. >> >> Shouldn't this be moved to DIBuilder and remove the dependency completely? >> >> -- >> cheers, >> --renato >> >> http://systemcall.org/ >> >> Reclaim your digital rights, eliminate DRM, learn more at...