search for: addmoduleflag

Adding the flags in an opt pass seems to do the trick. I added the flags as follows M.addModuleFlag(llvm::Module::Warning, "Dwarf Version", 3); M.addModuleFlag(llvm::Module::Error, "Debug Info Version", llvm::DEBUG_METADATA_VERSION); llvm-dwarfdump and addr2line now point at a line in .ll files, not the source files. Thanks! /Muneeb On 15 Oct...

...t;x86-64" "target-features"="+fxsr,+mmx,+sse,+sse2,+x87" "unsafe-fp-math"="false" "use-soft-float"="false" } Am I correct in assuming these are actually called flags, and they're accessed using Module::getModuleFlag() and Module::addModuleFlag()? Toshi -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20170502/50f18580/attachment.html>

On Wed, Oct 15, 2014 at 9:04 AM, Adrian Prantl <aprantl at apple.com> wrote: > I have no experience with debug-ir, but is it possible that the debug-ir > pass never sets the debug info version? There should be a named metadata > node > !llvm.module.flags = !{..., !123} > !123 = metadata !{i32 1, metadata !"Debug Info Version", i32 2} > in the .ll output. If

...d and computed >> when instantiating the TargetMachine, and TragetMachine constructor doesn't >> have IR as argument. >> > > Could you look into the other module level metadata to understand/explain > that, as it may help inform the design here? > > I grep "addModuleFlag" in clang and list all module level metadata: "NumRegisterParameters": implement __attribute((regparm(3))) which is x86 specific feature and used in X86TargetLowering phase. "cfguard": implement Control Flow Guard (Check mechanism) in IR level pass. "StrictVTablePoin...

...nd computed > when instantiating the TargetMachine, and TragetMachine constructor doesn't > have IR as argument. > > > > Could you look into the other module level metadata to > understand/explain that, as it may help inform the design here? > > > > I grep "addModuleFlag" in clang and list all module level metadata: > > > > "NumRegisterParameters": implement __attribute((regparm(3))) which is > x86 specific feature and used in X86TargetLowering phase. > > "cfguard": implement Control Flow Guard (Check mechanism) in IR...

> On Jan 6, 2018, at 4:33 PM, Sean Silva <chisophugis at gmail.com> wrote: > > > > On Jan 6, 2018 12:05 PM, "Saleem Abdulrasool via llvm-dev" <llvm-dev at lists.llvm.org <mailto:llvm-dev at lists.llvm.org>> wrote: >> On Jan 5, 2018, at 4:35 PM, Cary Coutant <ccoutant at gmail.com <mailto:ccoutant at gmail.com>> wrote: >>

...chine, and TragetMachine constructor doesn't >>> have IR as argument. >>> > >>> > Could you look into the other module level metadata to >>> understand/explain that, as it may help inform the design here? >>> > >>> > I grep "addModuleFlag" in clang and list all module level metadata: >>> > >>> > "NumRegisterParameters": implement __attribute((regparm(3))) which is >>> x86 specific feature and used in X86TargetLowering phase. >>> > "cfguard": implement Control Flo...

...d it now and it is very easy to switch to CodeView. >>>>>>>>>> For the ones interested : you just have to give your TargetTriple to your >>>>>>>>>> llvm::Module used for JIT and then call >>>>>>>>>> module->addModuleFlag(llvm::Module::Warning, "CodeView", 1) to tell the >>>>>>>>>> AsmPrinter this module prefer CodeView instead of Dwarf. >>>>>>>>>> I've checked the content of my .obj file, and there is valid >>>>>>>>&gt...

That’s a good question, by default when emitting the object file I choose COFF but it embeds dwarf and not codeview in the end.. there probably is a way to do it or at least it must be implemented if not yet.. Lets imagine I manage to do that.. when you say there is nothing to do, I still must have a PDBFileBuilder to copy the codeview data inside the EXE PDB right ? I cannot insert them easily in

...easy to switch to CodeView. >>>>>>>>>>>> For the ones interested : you just have to give your TargetTriple to your >>>>>>>>>>>> llvm::Module used for JIT and then call >>>>>>>>>>>> module->addModuleFlag(llvm::Module::Warning, "CodeView", 1) to tell the >>>>>>>>>>>> AsmPrinter this module prefer CodeView instead of Dwarf. >>>>>>>>>>>> I've checked the content of my .obj file, and there is valid >>>>&gt...

...etadata *, 3> Vals; + Vals.push_back(MDB.createString(E.first.first)); + Vals.push_back(MDB.createString(E.first.second)); + Vals.push_back(MDB.createConstant( + ConstantInt::get(Type::getInt64Ty(Context), E.second))); + Nodes.push_back(MDNode::get(Context, Vals)); + } + + M.addModuleFlag(Module::Append, "CFG Profile", MDNode::get(Context, Nodes)); + + return true; +} + +char CFGProfilePass::ID = 0; +INITIALIZE_PASS_BEGIN(CFGProfilePass, "cfg-profile", + "Generate profile information from the CFG.", false, false) + INITIALIZE_PASS_DEPENDENCY(BlockFre...

David Blaikie via llvm-dev <llvm-dev at lists.llvm.org> 於 2020年1月11日 週六 上午2:03寫道： > Ah, OK - thanks for walking me through that. > > Fair enough, I think I understand the issue/tradeoff now - and that the > other module level metadata don't currently influence the target > configuration at this level? > > I'm not sure, I only know that the target-abi is decided