mirror of
https://github.com/RPCS3/llvm-mirror.git
synced 2024-11-23 03:02:36 +01:00
Mirror of https://github.com/RPCS3/llvm-mirror
414ea6a00d
We have 2 DumpStyles currently: `class GNUStyle : public DumpStyle<ELFT>` and `class LLVMStyle : public DumpStyle<ELFT>`. The problem of `DumpStyle` interface is that almost for each method we provide `const ELFFile<ELFT> *` as argument. But in fact each of dump styles keeps `ELFDumper<ELFT> *Dumper` which can be used to get an object from. But since we use the `Obj` too often, I've decided to introduce a one more reference member instead of reading it from the `Dumper` each time: `const ELFFile<ELFT> &Obj;` This is kind of similar to `FileName` member which we have already: it is also used to store a the file name which can be read from `Dumper->getElfObject()->getFileName()`. I had to adjust the code which previously worked with a pointer to an object and now works with a reference. In a follow-up I am going to try to get rid of `const ELFObjectFile<ELFT>` arguments which are still passed to a set of functions. Differential revision: https://reviews.llvm.org/D87040 |
||
---|---|---|
benchmarks | ||
bindings | ||
cmake | ||
docs | ||
examples | ||
include | ||
lib | ||
projects | ||
resources | ||
runtimes | ||
test | ||
tools | ||
unittests | ||
utils | ||
.clang-format | ||
.clang-tidy | ||
.gitattributes | ||
.gitignore | ||
CMakeLists.txt | ||
CODE_OWNERS.TXT | ||
configure | ||
CREDITS.TXT | ||
LICENSE.TXT | ||
llvm.spec.in | ||
LLVMBuild.txt | ||
README.txt | ||
RELEASE_TESTERS.TXT |
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. LLVM is open source software. You may freely distribute it under the terms of the license agreement found in LICENSE.txt. Please see the documentation provided in docs/ for further assistance with LLVM, and in particular docs/GettingStarted.rst for getting started with LLVM and docs/README.txt for an overview of LLVM's documentation setup. If you are writing a package for LLVM, see docs/Packaging.rst for our suggestions.