search for: armmctargetdesc

Hi Fred, Thanks. How did you get to " The build log show this error: /Users/buildslave/as-bldslv9/lld-x86_64-darwin13/llvm.src/lib/Target/ARM/MCTargetDesc/ARMMCTargetDesc.cpp:92:11: error: enumeration values 'KalimbaSubArch_v3', 'KalimbaSubArch_v4', and 'KalimbaSubArch_v5' not handled in switch [-Werror,-Wswitch] switch (triple.getSubArch()) { " from here http://lab.llvm.org:8011/builders/lld-x86_64-darwin13/builds/2571 Sorry to se...

...nter(llvm::MCAsmInfo const&, unsigned int)': PPCMCTargetDesc.cpp:(.text._ZN4llvm14PPCInstPrinterC1ERKNS_9MCAsmInfoEj[llvm::PPCInstPrinter::PPCInstPrinter(llvm::MCAsmInfo const&, unsigned int)]+0x2d): undefined reference to `vtable for llvm::PPCInstPrinter' ../../lib/libLLVMARMDesc.a(ARMMCTargetDesc.cpp.o): In function `llvm::ARMInstPrinter::ARMInstPrinter(llvm::MCAsmInfo const&)': ARMMCTargetDesc.cpp:(.text._ZN4llvm14ARMInstPrinterC1ERKNS_9MCAsmInfoE[llvm::ARMInstPrinter::ARMInstPrinter(llvm::MCAsmInfo const&)]+0x2a): undefined reference to `vtable for llvm::ARMInstPrinter' .....

I'm working on lldb. I've just submitted a very small change (r217229) to Triple.h/.cpp. Soon after I get a mail subject: buildbot failure in LLVM on lld-x86_64-darwin13 Details: http://lab.llvm.org:8011/builders/lld-x86_64-darwin13/builds/2571 Blamelist: mg11 My small change certainly did not cause lldb's build to fail on my machine. I looked into the build-log:

ARM subtarget features are determined by parsing the target tuple string TT. (ParseARMTriple(StringRef TT) in ARMMCTargetDesc.cpp) In llc, the -march setting overrides the architecture specified in -mtriple. So when you invoke: $ llc -march arm -mtriple armv7-none-linux ... ParseARMTriple() will see TT == "arm-none-linux" instead of "armv7-none-linux". As a result, the target features will be set ge...

...2 ? Potential memory leak } Have not got why is this SparcTargetELFStreamer created dynamically and not assigned. Can anybody please explain is this a trick or a trouble? The similar pattern was detected in lib/Target/ARM/MCTargetDesc/ARMELFStreamer.cpp lib/Target/ARM/MCTargetDesc/ARMMCTargetDesc.cpp lib/Target/PowerPC/MCTargetDesc/PPCMCTargetDesc.cpp lib/Target/Mips/MCTargetDesc/MipsMCTargetDesc.cpp lib/Target/XCore/MCTargetDesc/XCoreMCTargetDesc.cpp lib/Target/Mips/MCTargetDesc/MipsMCTargetDesc.cpp lib/Target/Sparc/MCTargetDesc/SparcMCTargetDesc.cpp lib/MC/MCELFStreamer.cpp lib/MC/WinCOFF...

...posed to do, or do I have to figure it out from existing examples? On Sat, Mar 14, 2015 at 12:13 AM, Anton Korobeynikov < anton at korobeynikov.info> wrote: > You have to provide this function and initialize the whole MC > infrastructure. > > See e.g. lib/Target/ARM/MCTargetDesc/ARMMCTargetDesc.cpp > > On Sat, Mar 14, 2015 at 10:11 AM, Daniel Dilts <diltsman at gmail.com> wrote: > > Yes, llvm::InitializeAllTargetMCs(void) does seem to be autogenerated. > It > > is _LLVMInitializeFooTargetMC that I can't find documented anywhere. > > > > On Sat, M...

...t&, unsigned > int)': > PPCMCTargetDesc.cpp:(.text._ZN4llvm14PPCInstPrinterC1ERKNS_9MCAsmInfoEj[llvm::PPCInstPrinter::PPCInstPrinter(llvm::MCAsmInfo > const&, unsigned int)]+0x2d): undefined reference to `vtable for > llvm::PPCInstPrinter' > ../../lib/libLLVMARMDesc.a(ARMMCTargetDesc.cpp.o): In function > `llvm::ARMInstPrinter::ARMInstPrinter(llvm::MCAsmInfo const&)': > ARMMCTargetDesc.cpp:(.text._ZN4llvm14ARMInstPrinterC1ERKNS_9MCAsmInfoE[llvm::ARMInstPrinter::ARMInstPrinter(llvm::MCAsmInfo > const&)]+0x2a): undefined reference to `vtable for > llvm::AR...

On Mar 2, 2012, at 12:04 AM, David Meyer <pdox at google.com> wrote: > ARM subtarget features are determined by parsing the target tuple string TT. (ParseARMTriple(StringRef TT) in ARMMCTargetDesc.cpp) > > In llc, the -march setting overrides the architecture specified in -mtriple. So when you invoke: > > $ llc -march arm -mtriple armv7-none-linux ... > > ParseARMTriple() will see TT == "arm-none-linux" instead of "armv7-none-linux". As a result, the...

Yes, llvm::InitializeAllTargetMCs(void) does seem to be autogenerated. It is _LLVMInitializeFooTargetMC that I can't find documented anywhere. On Sat, Mar 14, 2015 at 12:05 AM, Anton Korobeynikov < anton at korobeynikov.info> wrote: > This function is autogenerated. You need also to change top-level > configure / cmake files. > > On Sat, Mar 14, 2015 at 8:38 AM, Daniel

...t/lib/builtins/CMakeFiles/clang_rt.builtins-armv6m.dir/arm/aeabi_memcpy.S.o -c ../projects/compiler-rt/lib/builtins/arm/aeabi_memcpy.S clang -cc1as: fatal error: error in backend: unsupported relocation on symbol [1920/5024] Building CXX object lib/Target/ARM/MCTargetDesc/CMakeFiles/LLVMARMDesc.dir/ARMMCTargetDesc.cpp.o ninja: build stopped: subcommand failed. ---- Relevant stuff: clang -cc1as: fatal error: error in backend: unsupported relocation on symbol Well, I don't know how to fix that. Any ideas ? Let me know if you need further info. -------------- next part -------------- An HTML attachment...

On 12 May 2014 15:11, Tim Northover <t.p.northover at gmail.com> wrote: > It sounds like you're using the wrong triple. Even on Windows you > should be able to output ELF if you compile with (say) "clang -target > arm-none-eabi". Or not using a triple at all. Windows on ARM support is coming along, I bet it defaults to WoA and outputs COFF or whatever. cheers,

I am having an issue with MCJIT on the ppc64 machine architecture. The symptom is that for a particular IR function the target machine won't emit neither an object nor an assembly file and subsequent calling the pointer to function results in a segfault. My application generates on the fly several functions with the builder and executes them with the MCJIT engine. I came across this