search for: llvm_all_targets

Hello. Excuse me. Why CMakeLists.txt from llvm-3.9.1.src does not contain WebAssembly target? So, it is like set(LLVM_ALL_TARGETS AArch64 AMDGPU ARM BPF Hexagon Mips MSP430 NVPTX PowerPC Sparc SystemZ X86 XCore ) but not like set(LLVM_ALL_TARGETS AArch64 AMDGPU ARM BPF Hexagon Mips MSP430 NVPTX PowerPC Sparc SystemZ Webassembly X86 XCore ) ? Is WebAssembly work...

because on windows platform. i686-pc-winnt is not mature and even don't working. So the it's better to set it to mingw. And also those spaces and indent modify is just because of the original indent is not consistent. Also, now msvc support multiple target. So it's better to set it as ${LLVM_ALL_TARGETS} It's can working, why not set it to:. -- 此致 礼 罗勇刚 Yours sincerely, Yonggang Luo

...umentation here: http://llvm.org/docs/WritingAnLLVMBackend.html The section on the build system seems to be out of date, or maybe I don't understand it. I copied the Sparc target to a directory (Foo for the example), added Foo to the subdirectories list in llvm\lib\Target\LLVMBuild.txt and to LLVM_ALL_TARGETS in llvm\CMakeLists.txt. I removed the files except for FooTargetMachine.cpp and FooTargetMachine.h. FooTargetMachine is not completed yet, but I was trying to compile and get linker errors about _LLVMInitializeFooTargetMC referenced in function void llvm::InitializeAllTargetMCs(void). I do not s...

...VMBackend.html > > > > The section on the build system seems to be out of date, or maybe I don't > > understand it. I copied the Sparc target to a directory (Foo for the > > example), added Foo to the subdirectories list in > > llvm\lib\Target\LLVMBuild.txt and to LLVM_ALL_TARGETS in > > llvm\CMakeLists.txt. I removed the files except for FooTargetMachine.cpp > > and FooTargetMachine.h. > > > > FooTargetMachine is not completed yet, but I was trying to compile and > get > > linker errors about _LLVMInitializeFooTargetMC referenced in functio...

...f the > original indent is not consistent. One patch, one fix. Every svn commit must have a precise purpose and be as concise as possible. If you want to fix whitespace inconsistencies, submit a separate patch. > Also, now msvc support multiple target. So it's better to set it as > ${LLVM_ALL_TARGETS} > It's can working, why not set it to:. I think most LLVM users on Windows are interested on X86 only. This saves a lot of time on the build process and creates smaller executables. Anyways, it they want all targets, it is simply a matter of passing -DLLVM_TARGETS_TO_BUILD=all on the cmake...

greetings I am new to this list. I have recently compiled llvm-3.3 from sources. My machine has these: --cpu -amd64 --os- clbfs 64bit -linux3 series kernel --C/C++ compiler -modern versions gcc My preferred build tool is cmake. llvm is needed for MesaLib and the autotools build of llvm allows this option:- --enable-experimental-targets=R600 ( for example described here:

...vm-3.(2,3,4) R600 was added to the list of known targets on the top-level CMakeLists.txt on June 22. So you can grab the LLVM development sources from svn or git and it should work (TM). If you wish to use LLVM 3.3, edit the top-level CMakeLists.txt file and add R600 to the list of known targets (LLVM_ALL_TARGETS). Then build as usual.

...on the build system seems to be out of date, or maybe I > >> > don't > >> > understand it. I copied the Sparc target to a directory (Foo for the > >> > example), added Foo to the subdirectories list in > >> > llvm\lib\Target\LLVMBuild.txt and to LLVM_ALL_TARGETS in > >> > llvm\CMakeLists.txt. I removed the files except for > >> > FooTargetMachine.cpp > >> > and FooTargetMachine.h. > >> > > >> > FooTargetMachine is not completed yet, but I was trying to compile and > >> > get > >...

...ion: 239035 > > Include BPF target in CMake builds. > > Modified: > llvm/trunk/CMakeLists.txt > > --- llvm/trunk/CMakeLists.txt (original) > +++ llvm/trunk/CMakeLists.txt Thu Jun 4 07:51:20 2015 > @@ -169,6 +169,7 @@ set(LLVM_INCLUDE_DIR ${CMAKE_CURRENT_BIN > set(LLVM_ALL_TARGETS > AArch64 > ARM > + BPF > CppBackend wow :) this is what I wanted to propose for the last few months. I had a chat with Chandler about graduating BPF backend from experimental, but I want to make sure everyone is ok before proceeding. Current status of it: - running on x64, a...

Hello, I have successfully build the newest llvm from git source, and I would like to do some experiments on target AVR. Does "make check-all" cover AVR? All I need some extra steps to test AVR? I have neither AVR simulator nor real AVR board connected. Thank you. -------------- next part -------------- An HTML attachment was scrubbed... URL:

...eptional in its dependencies, except for being lexicographically >the first target. I'd be interested in your results if AArch64 was >disabled. I can't say for sure if this is a new problem but we've been building on this machine for a few weeks now. I commented out AArch64 from LLVM_ALL_TARGETS and rebuilt but I can't reproduce the error in this case--it appears to be AArch64 specific. One thing I forgot to mention is that our build machines use ccache. When I don't use ccache I can't reproduce the error either. However, I don't think ccache is the problem it just makes t...

On Sun, Aug 9, 2009 at 10:03 AM, Óscar Fuentes<ofv at wanadoo.es> wrote: >> Also, now msvc support multiple target. So it's better to set it as >> ${LLVM_ALL_TARGETS} >> It's can working, why not set it to:. > > I think most LLVM users on Windows are interested on X86 only. This > saves a lot of time on the build process and creates smaller > executables. Anyways, it they want all targets, it is simply a matter of > passing -DLLVM_TARGE...

Hi Paul, > I'm getting a "random" build failure related to AArch64 when building with cmake. > The build is running with -j32 so it seems that there is some dependency issue > that causes the build to fail when things build in a certain order. > 3008 make[2]: *** No rule to make target `lib/Target/AArch64/AArch64GenDAGISel.inc', needed by Hmm. That file's

Hi, I'm getting a "random" build failure related to AArch64 when building with cmake. The build is running with -j32 so it seems that there is some dependency issue that causes the build to fail when things build in a certain order. Is anyone else seeing this problem? paul 3008 make[2]: *** No rule to make target `lib/Target/AArch64/AArch64GenDAGISel.inc', needed by

Hello all, I am a beginner of LLVM and want to add a new Target for LLVM. I follow the document (http://llvm.org/docs/WritingAnLLVMBackend.html) to modify autotools/configure.ac. However when I type ./AutoRegen.sh There is an error that "Your autoconf was not detected as being 2.60" I download the source of autoconf 2.60 and install it. And there is the other error that "Your

...struction: `add.w ' /run/user/1000/add-91f569.s:20: Error: no such instruction: `pop.w r4' clang-6.0: error: assembler command failed with exit code 1 (use -v to see invocation) It looks like msp430 is in the non-experimental target list: # List of all targets to be built by default: set(LLVM_ALL_TARGETS AArch64 AMDGPU ARM BPF Hexagon Lanai Mips MSP430 NVPTX PowerPC Sparc SystemZ X86 XCore ) Is msp430 supported? -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20180616/8c48c5c4/at...

Dear testers, 5.0.0-rc3 was just tagged. This is a release candidate in the real sense: if nothing bad comes up in testing, this is what the release is going to look like. Please build, test and upload binaries to the sftp (use the /data/testers-uploads/ directory) and let me know what issues remain. I know we're a little bit behind schedule, but hopefully we can get to 'final'