Displaying 3 results from an estimated 3 matches for "checkbitcodeoutputtoconsol".
Did you mean:
checkbitcodeoutputtoconsole
2007 Dec 06
0
[LLVMdev] 2.1 compile problem with undefined symbols
...ake tools-only
...
llvm[2]: Linking Release executable opt (without symbols)
/usr/bin/ld: warning prebinding disabled because of undefined symbols
/usr/bin/ld: Undefined symbols:
llvm::createGVNPass()
llvm::createGVNPREPass()
llvm::createLoopUnswitchPass(bool)
llvm::createLoopIndexSplitPass()
llvm::CheckBitcodeOutputToConsole(std::basic_ostream<char,
std::char_traits<char> >*, bool)
llvm::createScalarReplAggregatesPass(int)
llvm::createRedundantLoadEliminationPass()
collect2: ld returned 1 exit status
2007 Jul 05
2
[LLVMdev] PATCH (rest of code changes) "bytecode" --> "bitcode"
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
2011 Apr 05
3
[LLVMdev] Building LLVM on Solaris/Sparc
...ParallelAssert/llvm-objects/tools/opt/Debug+Asserts/opt.o
llvm::DominanceFrontier::ID
/n/fs/scratch/tpondich/ParallelAssert/llvm-objects/tools/opt/Debug+Asserts/GraphPrinters.o
llvm::createRegionOnlyPrinterPass()
/n/fs/scratch/tpondich/ParallelAssert/llvm-objects/tools/opt/Debug+Asserts/opt.o
llvm::CheckBitcodeOutputToConsole(llvm::raw_ostream&,
bool)/n/fs/scratch/tpondich/ParallelAssert/llvm-objects/tools/opt/Debug+Asserts/opt.o
llvm::createPostDomOnlyViewerPass()
/n/fs/scratch/tpondich/ParallelAssert/llvm-objects/tools/opt/Debug+Asserts/opt.o
vtable for llvm::cl::opt<std::basic_string<char, std::char_traits...