Go to file

Pavel Labath ebe2f56030 DWARFDebugLoclists: add location list "interpretation" logic Summary: This patch extracts the logic for computing the "absolute" locations, which was partially present in the debug_loclists dumper, completes it, and moves it into a separate function. This makes it possible to later reuse the same logic for uses other than dumping. The dumper is changed to reuse the location list interpreter, and its format is changed somewhat. In "verbose" mode it prints the "raw" value of a location list, the interpreted location (if available) and the expression itself. In non-verbose mode it prints only one of the location forms: it prefers the interpreted form, but falls back to the "raw" format if interpretation is not possible (for instance, because we were not given a base address, or the resolution of indirect addresses failed). This patch also undos some of the changes made in D69672, namely the part about making all functions static. The main reason for this is that I learned that the original approach (dumping only fully resolved locations) meant that it was impossible to rewrite one of the existing tests. To make that possible (and make the "inline location" dump work in more cases), I now reuse the same dumping mechanism as is used for section-based dumping. As this required having more objects know about the various location lists classes, it seemed like a good idea to create an interface abstracting the difference between them. Therefore, I now create a DWARFLocationTable class, which will serve as a base class for the location list classes. DWARFDebugLoclists is made to inherit from that. DWARFDebugLoc will follow. Another positive effect of this change is that section-based dumping code will not need to use templates (as originally) envisioned, and that the argument lists of the dumping functions become shorter. Reviewers: dblaikie, probinson, JDevlieghere, aprantl, SouraVX Subscribers: hiraditya, llvm-commits Tags: #llvm Differential Revision: https://reviews.llvm.org/D70081		2019-11-12 10:40:13 +01:00
clang	[clang-format] [PR36294] AlwaysBreakAfterReturnType works incorrectly for some operator functions	2019-11-12 09:25:00 +00:00
clang-tools-extra	[clangd] Fix crash in DefineInline::prepare()	2019-11-11 19:01:06 +01:00
compiler-rt	[scudo][standalone] Match function name change to bionic name change.	2019-11-11 09:41:57 -08:00
debuginfo-tests	[debuginfo] Update test to account for missing __debug_macinfo	2019-11-11 10:40:47 -08:00
libc	Illustrate a redirector using the example of round function from math.h.	2019-11-01 11:06:12 -07:00
libclc	libclc: Drop the old python based build system	2019-11-08 09:59:40 -05:00
libcxx	[libc++][P0980] Marked member functions move/copy/assign of char_traits constexpr.	2019-11-11 09:49:48 -08:00
libcxxabi	[demangle] NFC: get rid of NodeOrString	2019-11-04 12:17:12 -08:00
libunwind	change LLVM_VERSION_SUFFIX default from svn to git	2019-11-11 09:10:20 -08:00
lld	[MC] Emit unused undefined symbol even if its binding is not set	2019-11-08 14:47:48 -08:00
lldb	[lldb] Add missing include to ObjCLanguage.cpp to fix build	2019-11-12 10:21:49 +01:00
llgo	IR: Support parsing numeric block ids, and emit them in textual output.	2019-03-22 18:27:13 +00:00
llvm	DWARFDebugLoclists: add location list "interpretation" logic	2019-11-12 10:40:13 +01:00
openmp	[openmp] [test] Skip one more test that kills NetBSD buildbot	2019-11-07 17:29:57 +01:00
parallel-libs	Fix typos throughout the license files that somehow I and my reviewers	2019-01-21 09:52:34 +00:00
polly	[www] More HTTPS and outdated link fixes.	2019-11-08 14:41:27 -08:00
pstl	[pstl] Allow customizing whether per-TU insulation is provided	2019-08-13 12:49:00 +00:00
.arcconfig	Update monorepo .arcconfig with new project callsign.	2019-01-31 14:34:59 +00:00
.clang-format	Add .clang-tidy and .clang-format files to the toplevel of the	2019-01-29 16:43:16 +00:00
.clang-tidy	Disable tidy checks with too many hits	2019-02-01 11:20:13 +00:00
.git-blame-ignore-revs	Add LLDB reformatting to .git-blame-ignore-revs	2019-09-04 09:31:55 +00:00
.gitignore	Add a newline at the end of the file	2019-09-04 06:33:46 +00:00
README.md	Add beginning of LLVM's GettingStarted to GitHub readme	2019-10-23 18:03:37 -07:00

README.md

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.

Overview

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.

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:
- cd llvm-project
- mkdir build
- cd build
- 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 -DLLVM_ENABLE_PROJECTS="clang;libcxx;libcxxabi".
  - -DCMAKE_INSTALL_PREFIX=directory --- Specify for directory the full pathname 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).
- Run your build tool of choice!
  - 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 build 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 make -j NNN (NNN is the number of parallel jobs, use e.g. 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.