search for: haslinkoncelinkage

...bilityTypes A, return A; if (B == GlobalValue::HiddenVisibility) return B; - if (A == GlobalValue::ProtectedVisibility) - return A; return B; } @@ -520,15 +518,9 @@ static ld_plugin_status claim_file_hook(const ld_plugin_input_file *file, Res.IsLinkonceOdr &= GV->hasLinkOnceLinkage(); Res.Visibility = getMinVisibility(Res.Visibility, GV->getVisibility()); switch (GV->getVisibility()) { - case GlobalValue::DefaultVisibility: - sym.visibility = LDPV_DEFAULT; - break; case GlobalValue::HiddenVisibility: sym.visibility = LDPV...

...t the same failure as I did with foo.bc. That is not the case. I get a different assertion failure when I compile either of them with llc which is as follows: llc: <llvm-src>/llvm/lib/CodeGen/AsmPrinter/DwarfWriter.cpp:2808: void llvm::DwarfDebug::ConstructCompileUnits(): Assertion `Root->hasLinkOnceLinkage() && Root->hasOneUse() && "Malformed compile unit descriptor anchor type"' failed. This makes it hard for me to easily create a test case and submit a bug report. Hence, I thought I should take this opportunity to delve deeper into LLVM and look at this issue. An...

...t; foo.bc. That is not the case. I get a different assertion failure > when I compile either of them with llc which is as follows: > > llc: <llvm-src>/llvm/lib/CodeGen/AsmPrinter/DwarfWriter.cpp:2808: > void llvm::DwarfDebug::ConstructCompileUnits(): Assertion `Root- > >hasLinkOnceLinkage() && Root->hasOneUse() && "Malformed compile > unit descriptor anchor type"' failed. This is because bugpoint tool does not understand debug info intrinsics. To avoid this, when you generate foo.bc with -emit-llvm switch, do not use -g on the llvm-gcc comman...

Hi Bharadwaj, > I get the following error during compilation using the LLVM cross-compiler > (x86_64->arm). > > error: nested functions are disabled, use -fnested-functions to re-enable yes, nested functions are disabled by default in llvm-gcc (not sure why - maybe a historical hang over from the days when they were not supported?). > With -fnested-functions switch, I get the

I get the following error during compilation using the LLVM cross-compiler (x86_64->arm). error: nested functions are disabled, use -fnested-functions to re-enable With -fnested-functions switch, I get the following error: <llvm-src-dir>/llvm/lib/Target/ARM/ARMISelLowering.cpp:1439: virtual llvm::SDValue llvm::ARMTargetLowering::LowerOperation(llvm::SDValue, llvm::SelectionDAG&):

Here is the bulk of the sanitizing. My residual doubts center around the question whether we still do/want to support (un)compressed *byte*code in 2.0/2.1. I need a definitive word on this to proceed. My understanding is that bytecode is already gone, but there are still some functions/enums that really deal with *byte*code (instead of *bit*code). I did not touch those areas, so the attached