[lldb][Target] Allow eLanguageTypeAssembly to use ScratchTypeSystemClang (#183771) After cleaning up some of our `LanguageType`/`SourceLangage` round-tripping (see `7f51a2a47d2e706d04855b0e41690ebafa2b3238`), a CU with `DW_LANG_MIPS_Assembler` will get a language type of `eLanguageTypeAssembly` (as opposed to `eLanguageTypeMipsAssembler`). Reason being that there is no `DW_LNAME_` (DWARFv6 language code) for `MIPS Assembler`, only for generic `Assembly`. So it's not possible to round-trip cleanly between pre-DWARFv6 and DWARFv6 language codes, which LLDB relies on for storing language types (and will lean into more heavily in the future). This broke a special provision we have where we allow `ScratchTypeSystemClang` to be used when evaluating expressions in assembly CUs (i.e., CUs where the debug-info explicitly sets the language to assembly). If we ever want to distinguish MIPS from other Assembly, the proper way to do so is introduce a `DW_LNAME_Mips_Assembler`. For now, this patch adds another case for `eLanguageTypeAssembly` in `GetScratchTypeSystemForLanguage`. The test is a bit quirky because it checks for error messages in all cases. For the `TypeSystem`s to exist we would have to initialize the `TypeSystem` plugins, which I couldn't find a precedent for. But happy to hear other suggestions for testing Fixes https://github.com/llvm/llvm-project/issues/183388
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.
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.
Join the LLVM Discourse forums, Discord chat, LLVM Office Hours or Regular sync-ups.
The LLVM project has adopted a code of conduct for participants to all modes of communication within the project.