26ca2f47c1
Querying the debug_str_offsets section requires parsing the top level DIE of the CU (as well as the section itself); the current getter, however, assumes this is done elsewhere. This patch changes the getter behavior to match what is done in other getter methods (e.g. `getCompilationDir` or `getVariableForAddress`), in other words, `extractDIEsIfNeeded` is now called prior to returning the debug_str_offsets contributions for the Unit. One way in which this bug manifested is when `dwarfdump --debug-str-offsets` is invoked: because the DIEs are never parsed, we incorrectly print an empty section (with no warnings or errors). Differential Revision: https://reviews.llvm.org/D159484
The LLVM Compiler Infrastructure
Welcome to the LLVM project!
This repository contains the source code for LLVM, a toolkit for the construction of highly optimized compilers, optimizers, and run-time environments.
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 convert them into object files. Tools include an assembler, disassembler, bitcode analyzer, and bitcode optimizer.
C-like languages use the Clang frontend. 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
Consult the Getting Started with LLVM page for information on building and running LLVM.
For information on how to contribute to the LLVM project, please take a look at the Contributing to LLVM guide.
Getting in touch
Join the LLVM Discourse forums, Discord chat, or #llvm IRC channel on OFTC.
The LLVM project has adopted a code of conduct for participants to all modes of communication within the project.