LLVM for NEC SX-Aurora VE
This repository is a clone of public LLVM repository (https://github.com/llvm/llvm-project), plus experimental modifications which provide support for the NEC SX-Aurora TSUBASA Vector Engine (VE). See README_MORE.rst.
You can start with the PRM package.
% yum install \ https://sx-aurora.com/repos/veos/ef_extra/x86_64/llvm-ve-1.5.0-1.5.0-1.x86_64.rpm \ https://sx-aurora.com/repos/veos/ef_extra/x86_64/llvm-ve-link-1.5.0-1.x86_64.rpm
Then use clang like below. Clang++ is also available.
$ /opt/nec/nosupport/llvm-ve/clang -target ve-linux -O3 ...
- If you are interested in intrinsic functions for vector instructions, see the manual.
- If you are interested in the guided vectorization, or region vectorizer, see RV.
- If you want to build the llvm-ve, see llvm-dev and Compile.rst.
- Automatic vectorization is not supported.
The LLVM Compiler Infrastructure
This directory and its subdirectories contain source code for LLVM, a toolkit for the construction of highly optimized compilers, optimizers, and runtime environments.
Getting Started with the LLVM System
Taken from https://llvm.org/docs/GettingStarted.html.
Welcome to the LLVM project!
The LLVM project has multiple components. The core of the project is itself called "LLVM". This contains all of the tools, libraries, and header files needed to process intermediate representations and converts it into object files. Tools include an assembler, disassembler, bitcode analyzer, and bitcode optimizer. It also contains basic regression tests.
C-like languages use the Clang front end. This component compiles C, C++, Objective C, and Objective C++ code into LLVM bitcode -- and from there into object files, using LLVM.
Getting the Source Code and Building LLVM
The LLVM Getting Started documentation may be out of date. The Clang Getting Started page might have more accurate information.
This is an example workflow and configuration to get and build the LLVM source:
Checkout LLVM (including related subprojects like Clang):
git clone https://github.com/llvm/llvm-project.git
Or, on windows,
git clone --config core.autocrlf=false https://github.com/llvm/llvm-project.git
Configure and build LLVM and Clang:
cmake -G <generator> [options] ../llvm
Some common generators are:
Ninja--- for generating Ninja build files. Most llvm developers use Ninja.
Unix Makefiles--- for generating make-compatible parallel makefiles.
Visual Studio--- for generating Visual Studio projects and solutions.
Xcode--- for generating Xcode projects.
Some Common options:
-DLLVM_ENABLE_PROJECTS='...'--- semicolon-separated list of the LLVM subprojects you'd like to additionally build. Can include any of: clang, clang-tools-extra, libcxx, libcxxabi, libunwind, lldb, compiler-rt, lld, polly, or debuginfo-tests.
For example, to build LLVM, Clang, libcxx, and libcxxabi, use
-DCMAKE_INSTALL_PREFIX=directory--- Specify for directory the full pathname of where you want the LLVM tools and libraries to be installed (default
-DCMAKE_BUILD_TYPE=type--- Valid options for type are Debug, Release, RelWithDebInfo, and MinSizeRel. Default is Debug.
-DLLVM_ENABLE_ASSERTIONS=On--- Compile with assertion checks enabled (default is Yes for Debug builds, No for all other build types).
Run your build tool of choice!
The default target (i.e.
make) will build all of LLVM.
ninja check-all) will run the regression tests to ensure everything is in working order.
CMake will generate build targets for each tool and library, and most LLVM sub-projects generate their own
Running a serial build will be slow. To improve speed, try running a parallel build. That's done by default in Ninja; for
make -j NNN(NNN is the number of parallel jobs, use e.g. number of CPUs you have.)
For more information see CMake