search for: initializealltargetinfo

...uccessfully check out, build and test with the new changes. The x86_64 build on the buildbot is failing, however. Here's the build error: llvm[2]: Linking Debug+Asserts executable llvm-mc /home/baldrick/osuosl/slave/llvm-x86_64/llvm/tools/llvm-mc/Debug+Asserts/llvm-mc.o: In function `llvm::InitializeAllTargetInfos()': llvm-mc.cpp:(.text._ZN4llvm24InitializeAllTargetInfosEv[llvm::InitializeAllTargetInfos()]+0x5): undefined reference to `LLVMInitializeHexagonTargetInfo' /home/baldrick/osuosl/slave/llvm-x86_64/llvm/tools/llvm-mc/Debug+Asserts/llvm-mc.o: In function `llvm::InitializeAllTargetMCs()':...

...heck out, build and test with the new changes. The x86_64 build on the buildbot is failing, however. Here's the build error: > > llvm[2]: Linking Debug+Asserts executable llvm-mc > /home/baldrick/osuosl/slave/llvm-x86_64/llvm/tools/llvm-mc/Debug+Asserts/llvm-mc.o: In function `llvm::InitializeAllTargetInfos()': > llvm-mc.cpp:(.text._ZN4llvm24InitializeAllTargetInfosEv[llvm::InitializeAllTargetInfos()]+0x5): undefined reference to `LLVMInitializeHexagonTargetInfo' > /home/baldrick/osuosl/slave/llvm-x86_64/llvm/tools/llvm-mc/Debug+Asserts/llvm-mc.o: In function `llvm::InitializeAllTargetM...

...>> the new changes. The x86_64 build on the buildbot is failing, >> however. Here's the build error: >> >> llvm[2]: Linking Debug+Asserts executable llvm-mc >> /home/baldrick/osuosl/slave/llvm-x86_64/llvm/tools/llvm-mc/Debug+Asserts/llvm-mc.o: In function `llvm::InitializeAllTargetInfos()': >> llvm-mc.cpp:(.text._ZN4llvm24InitializeAllTargetInfosEv[llvm::InitializeAllTargetInfos()]+0x5): undefined reference to `LLVMInitializeHexagonTargetInfo' >> /home/baldrick/osuosl/slave/llvm-x86_64/llvm/tools/llvm-mc/Debug+Asserts/llvm-mc.o: In function `llvm::InitializeAl...

...w changes. The x86_64 build on the buildbot is failing, however. Here's the build error: >>>> >>>> llvm[2]: Linking Debug+Asserts executable llvm-mc >>>> /home/baldrick/osuosl/slave/llvm-x86_64/llvm/tools/llvm-mc/Debug+Asserts/llvm-mc.o: In function `llvm::InitializeAllTargetInfos()': >>>> llvm-mc.cpp:(.text._ZN4llvm24InitializeAllTargetInfosEv[llvm::InitializeAllTargetInfos()]+0x5): undefined reference to `LLVMInitializeHexagonTargetInfo' >>>> /home/baldrick/osuosl/slave/llvm-x86_64/llvm/tools/llvm-mc/Debug+Asserts/llvm-mc.o: In function `ll...

...uild on the buildbot is failing, however. Here's the build error: >>>>>> >>>>>> llvm[2]: Linking Debug+Asserts executable llvm-mc >>>>>> /home/baldrick/osuosl/slave/llvm-x86_64/llvm/tools/llvm-mc/Debug+Asserts/llvm-mc.o: In function `llvm::InitializeAllTargetInfos()': >>>>>> llvm-mc.cpp:(.text._ZN4llvm24InitializeAllTargetInfosEv[llvm::InitializeAllTargetInfos()]+0x5): undefined reference to `LLVMInitializeHexagonTargetInfo' >>>>>> /home/baldrick/osuosl/slave/llvm-x86_64/llvm/tools/llvm-mc/Debug+Asserts/llvm-mc.o:...

...with the new changes. The x86_64 build on the buildbot is failing, however. Here's the build error: >>> >>> llvm[2]: Linking Debug+Asserts executable llvm-mc >>> /home/baldrick/osuosl/slave/llvm-x86_64/llvm/tools/llvm-mc/Debug+Asserts/llvm-mc.o: In function `llvm::InitializeAllTargetInfos()': >>> llvm-mc.cpp:(.text._ZN4llvm24InitializeAllTargetInfosEv[llvm::InitializeAllTargetInfos()]+0x5): undefined reference to `LLVMInitializeHexagonTargetInfo' >>> /home/baldrick/osuosl/slave/llvm-x86_64/llvm/tools/llvm-mc/Debug+Asserts/llvm-mc.o: In function `llvm::Init...

...he buildbot is >>>>> failing, however. Here's the build error: >>>>> >>>>> llvm[2]: Linking Debug+Asserts executable llvm-mc >>>>> /home/baldrick/osuosl/slave/llvm-x86_64/llvm/tools/llvm-mc/Debug+Asserts/llvm-mc.o: In function `llvm::InitializeAllTargetInfos()': >>>>> llvm-mc.cpp:(.text._ZN4llvm24InitializeAllTargetInfosEv[llvm::InitializeAllTargetInfos()]+0x5): undefined reference to `LLVMInitializeHexagonTargetInfo' >>>>> /home/baldrick/osuosl/slave/llvm-x86_64/llvm/tools/llvm-mc/Debug+Asserts/llvm-mc.o: In func...

...buildbot is failing, however. Here's the build error: >>>>>>> >>>>>>> llvm[2]: Linking Debug+Asserts executable llvm-mc >>>>>>> /home/baldrick/osuosl/slave/llvm-x86_64/llvm/tools/llvm-mc/Debug+Asserts/llvm-mc.o: In function `llvm::InitializeAllTargetInfos()': >>>>>>> llvm-mc.cpp:(.text._ZN4llvm24InitializeAllTargetInfosEv[llvm::InitializeAllTargetInfos()]+0x5): undefined reference to `LLVMInitializeHexagonTargetInfo' >>>>>>> /home/baldrick/osuosl/slave/llvm-x86_64/llvm/tools/llvm-mc/Debug+Asserts/ll...

...where I have add to compiler settings: `llvm-config --cxxflags` and to linker settings: `llvm-config --ldflags --system-libs --libs core orcjit native` In 2 to 7 is OK, but sample 8 has errors: ||=== Build: Debug in Chapter8 (compiler: LLVM Clang Compiler) ===| obj/Debug/toy.o||In function `llvm::InitializeAllTargetInfos()':| /usr/local/include/llvm/Config/Targets.def|26|undefined reference to `LLVMInitializeAArch64TargetInfo'| /usr/local/include/llvm/Config/Targets.def|27|undefined reference to `LLVMInitializeAMDGPUTargetInfo'| /usr/local/include/llvm/Config/Targets.def|28|undefined reference to `LLVM...

...d by user code only once at startup, there does not seem to be a fundamental need for them to be inlined. This is why I propose to make them non-inline, normal functions that get declared in their current header and defined in lib/IR/Core.cpp. The list of functions affected by this is: void llvm::InitializeAllTargetInfos () void llvm::InitializeAllTargets () void llvm::InitializeAllTargetMCs () void llvm::InitializeAllAsmPrinters () void llvm::InitializeAllAsmParsers () void llvm::InitializeAllDisassemblers () bool llvm::InitializeNativeTarget () bool llvm::InitializeNativeTargetAsmPrinter () bool llvm::Initialize...

...failing, however. Here's the build error: >>>>>>>> >>>>>>>> llvm[2]: Linking Debug+Asserts executable llvm-mc >>>>>>>> /home/baldrick/osuosl/slave/llvm-x86_64/llvm/tools/llvm-mc/Debug+Asserts/llvm-mc.o: In function `llvm::InitializeAllTargetInfos()': >>>>>>>> llvm-mc.cpp:(.text._ZN4llvm24InitializeAllTargetInfosEv[llvm::InitializeAllTargetInfos()]+0x5): undefined reference to `LLVMInitializeHexagonTargetInfo' >>>>>>>> /home/baldrick/osuosl/slave/llvm-x86_64/llvm/tools/llvm-mc/Debug+As...

I believe we'd need LLVMBuild.txt even in autoconf build - for bunch of autogenerated stuff, e.g. list of all asmprinters / asmparsers / InitializeAllTargetInfos, etc., since targets are not autoregistered anymore. On Mon, Mar 9, 2015 at 7:20 PM, Eric Christopher <echristo at gmail.com> wrote: > Hi Neil, > > Weird, I'd think the cmake build should probably do something similar to the > autoconf build if possible and just have subdire...

...SNIPPET ==== const std::string TripleStr = "i686-unknown-linux"; // hard coded for example const std::string FeatureStr = ""; // hard coded for example std::string Err; const Target* T; TargetMachine* TM = NULL; const TargetData* TD; // Or just call InitializeAllTargetInfos() and InitializeAllTargets() for all targets enabled by your LLVM build. LLVMInitializeX86TargetInfo(); LLVMInitializeX86Target(); T = TargetRegistry::lookupTarget(TripleStr, Err); if(!Err.empty()) // error handling // Create TargetMachine TM = T->createTargetM...

Dear all I am trying to get the size of an LLVM pointer type. getPrimitiveSizeInBits() returns 0 for it and the documentation for isSized() suggest to use TargetData. I figured out from Kaleidoscope example that one can get a pointer to TagetData object through the execution engine but it seems to be an overkill. What is the right way to do it? Best regards, Victor -------------- next part

Mehdi, Teresa, Not sure if this is caused by one of your recent commits, or by someone else's, please excuse me if that's unrelated to your work... http://lab.llvm.org:8011/builders/sanitizer-x86_64-linux-fast/builds/542/steps/check-llvm%20asan/logs/stdio ==26383==ERROR: AddressSanitizer: initialization-order-fiasco on address 0x000002ef41d8 at pc 0x0000009d1aa5 bp 0x7ffd0cd72b50 sp

...does the kinds of things I want to do at the MC "layer". So, I'd like to be able to use a MCStreamer object directly to make some output file, and object ".o" would be just fine to start with. I seem to be able to create an aarch64 target without too much issue: llvm::InitializeAllTargetInfos(); llvm::InitializeAllTargetMCs(); llvm::InitializeAllAsmParsers(); llvm::InitializeAllDisassemblers(); std::string Error; std::string TripleName("aarch64-unknown-linux-gnu"); Triple TheTriple(Triple::normalize(TripleName)); const Target *TheTarget = TargetRegistry::lookup...

Hi Frédéric and LLVM, I managed to finally come back to this after quite a while. Frédéric, thank you very much for the pointer to your work; it’s saving me a lot of time! Unfortunately, I am running into one issue that my knowledge isn’t complete enough to solve on my own yet. The description of D6771 reads, "It requires a few preliminary patches like landing D6243 and adding a

I've managed to get 10.0.0 working now.. there were a couple things I had to adjust. The Kaleidoscope example had me doing this before creating the object file: llvm::InitializeAllTargetInfos(); llvm::InitializeAllTargets(); llvm::InitializeAllTargetMCs(); llvm::InitializeAllAsmParsers(); llvm::InitializeAllAsmPrinters(); It turns out I can get away with just this, since I'm not (yet) worried about targeting other machines: llvm::InitializeNativeTarget(); llvm::InitializeNativeTar...

Hey all, Quick query on out of tree target support - at present I can drop a folder Foo into <llvm>/lib/Target/Foo and use the CMake option LLVM_EXPERIMENTAL_TARGETS_TO_BUILD to pick up my target. The issue is that I still need to patch the one LLVMBuild.txt file in <llvm>/lib/Target with; |iff --git a/lib/Target/LLVMBuild.txt b/lib/Target/LLVMBuild.txt index 4112046..6e42cbe