commit | 541bead8b424c46b43b3d5fcf19377db70802573 | [log] [tgz] |
---|---|---|
author | vgxbj <higuoxing@gmail.com> | Sat Apr 04 18:17:58 2020 +0800 |
committer | vgxbj <higuoxing@gmail.com> | Sat Apr 04 18:45:52 2020 +0800 |
tree | 6519d900383829d687f68211ef3536fcd440e705 | |
parent | ebd5a1b0498ff0c7cf790f6d980db5a8a3e2bbb9 [diff] |
[Object] object::ELFObjectFile::dynamic_symbol_begin(): skip symbol index 0 Summary: Note: This revision is very similar to D62296. In D75756, we need `getDynamicSymbolIterators()` to skip first NULL symbol in `.dynsym`. And I believe it might be worth pointing this out in a separate patch to gather you experts' opinions. I have checked that current code base will not be affected by this change. ``` dynamic_symbol_begin() |- dynamic_symbol_end(): Ok `- getDynamicSymbolIterators() |- addDynamicElfSymbols(): llvm/tools/llvm-objdump/llvm-objdump.cpp, Line 934 | Ok, NULL symbol will be omitted by Line 945-947 | StringRef Name = unwrapOrError(Symbol.getName(), Obj->getName()); | if (Name.empty()) continue; |- dumpSymbolNameFromObject(): llvm/tools/llvm-nm/llvm-nm.cpp, Line 1192 | There's no test for dumping dynamic debugging symbol. This patch helps improve llvm-nm behavior. (we should add test for this later) `- computeSymbolSizes(): llvm/lib/Object/SymbolSize.cpp, Line 52 |- OProfileJITEventListener::notifyObjectLoaded(): llvm/lib/ExecutionEngine/OProfileJIT/OProfileJITEventListener.cpp, Line 92 | Ok, NULL symbol will be omitted by Line 94-95 | if (!Sym.getType() || *Sym.getType() != SF_Function) continue; |- IntelJITEventListener::notifyObjectLoaded(): llvm/lib/ExecutionEngine/IntelJITEvents/IntelJITEventListener.cpp, Line 98 | Ok, NULL symbol will be omitted by Line 124-126 (same as previous one) |- PerfJITEventListener::notifyObjectLoaded(): llvm/lib/ExecutionEngine/PerfJITEvents/PerfJITEventListener.cpp, Line 244 | Ok, NULL symbol will be omitted by Line 254-256, (same as previous one) |- SymbolizableObjectFile::create(): llvm/lib/DebugInfo/Symbolize/SymbolizableObjectFile.cpp, Line 73 | Ok, NULL symbol will be omitted by Line 75 | res->addSymbol() | In addSymbol(), Line 167-168 | if (!Sec || (Obj && Obj->section_end() == *Sec)) return std::error_code(); |- dumpCXXData(): llvm/tools/llvm-cxxdump/llvm-cxxdump.cpp, Line 189 | Ok, NULL symbol will be omitted by Line 199-202 | object::section_iterator SecI = *SecIOrErr; | // Skip external symbols. | if (SecI == Obj->section_end()) | continue; `- printLineInfoForInput(): llvm/tools/llvm-rtdyld/llvm-rtdyld.cpp, Line 418 Ok, NULL symbol will be omitted by Line 430-477 if (Type == object::SymbolRef::ST_Function) { ... } ``` Reviewers: grimar, jhenderson, MaskRay Reviewed By: jhenderson, MaskRay Subscribers: rupprecht, arphaman, llvm-commits Tags: #llvm Differential Revision: https://reviews.llvm.org/D76081
This directory and its sub-directories contain source code for LLVM, a toolkit for the construction of highly optimized compilers, optimizers, and run-time environments.
The README briefly describes how to get started with building LLVM. For more information on how to contribute to the LLVM project, please take a look at the Contributing to LLVM guide.
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.
Other components include: the libc++ C++ standard library, the LLD linker, and more.
The LLVM Getting Started documentation may be out of date. The Clang Getting Started page might have more accurate information.
This is an example work-flow and configuration to get and build the LLVM source:
Checkout LLVM (including related sub-projects 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:
cd llvm-project
mkdir build
cd build
cmake -G <generator> [options] ../llvm
Some common build system 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 sub-projects 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 -DLLVM_ENABLE_PROJECTS="clang;libcxx;libcxxabi"
.
-DCMAKE_INSTALL_PREFIX=directory
--- Specify for directory the full path name of where you want the LLVM tools and libraries to be installed (default /usr/local
).
-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).
cmake --build . [-- [options] <target>]
or your build system specified above directly.
The default target (i.e. ninja
or make
) will build all of LLVM.
The check-all
target (i.e. ninja check-all
) will run the regression tests to ensure everything is in working order.
CMake will generate targets for each tool and library, and most LLVM sub-projects generate their own check-<project>
target.
Running a serial build will be slow. To improve speed, try running a parallel build. That's done by default in Ninja; for make
, use the option -j NNN
, where NNN
is the number of parallel jobs, e.g. the number of CPUs you have.
For more information see CMake
Consult the Getting Started with LLVM page for detailed information on configuring and compiling LLVM. You can visit Directory Layout to learn about the layout of the source code tree.