llvm-project.git/llvm/lib/Support/CommandLine.cpp, branch users/nico/python-1

[NFC][ADT/Support] Add {} for else when if body has {} (#140758)

2025-05-21T20:19:09+00:00

[Support] Use range-based for loops (NFC) (#140401)

2025-05-18T00:01:05+00:00

[llvm] annotate interfaces in llvm/Support for DLL export (#136014)

2025-05-12T19:13:52+00:00

## Purpose

This patch is one in a series of code-mods that annotate LLVM’s public
interface for export. This patch annotates the `llvm/Support` library.
These annotations currently have no meaningful impact on the LLVM build;
however, they are a prerequisite to support an LLVM Windows DLL (shared
library) build.

## Background

This effort is tracked in #109483. Additional context is provided in
[this
discourse](https://discourse.llvm.org/t/psa-annotating-llvm-public-interface/85307),
and documentation for `LLVM_ABI` and related annotations is found in the
LLVM repo
[here](https://github.com/llvm/llvm-project/blob/main/llvm/docs/InterfaceExportAnnotations.rst).

The bulk of these changes were generated automatically using the
[Interface Definition Scanner (IDS)](https://github.com/compnerd/ids)
tool, followed formatting with `git clang-format`.

The following manual adjustments were also applied after running IDS on
Linux:
- Add `#include "llvm/Support/Compiler.h"` to files where it was not
auto-added by IDS due to no pre-existing block of include statements.
- Add `LLVM_ABI` to Windows-only code (auto generated with IDS on
Windows)
- Explicitly make classes non-copyable where needed to due IDS adding
`LLVM_ABI` at the class level
- Add `LLVM_TEMPLATE_ABI` and `LLVM_EXPORT_TEMPLATE` to exported
instantiated templates
- Add `LLVM_ABI_FRIEND` to a small number of `friend` function
declarations
- Add `LLVM_ABI` to a subset of private class methods and fields that
require export
- Add `LLVM_ABI` to a small number of symbols that require export but
are not declared in headers
- Add `LLVM_ABI` functions defined via X-macro

## Validation

Local builds and tests to validate cross-platform compatibility. This
included llvm, clang, and lldb on the following configurations:

- Windows with MSVC
- Windows with Clang
- Linux with GCC
- Linux with Clang
- Darwin with Clang

[llvm] Use StringRef::drop_back (NFC) (#139471)

2025-05-11T22:37:41+00:00

[llvm] Use llvm::append_range (NFC) (#133658)

2025-03-31T01:43:02+00:00

[NFC][Support] Create helper function to parse bool (#102818)

2024-08-13T03:49:18+00:00

Create a helper template function to parse bool, to eliminate code
duplication.

[Support] Use range-based for loops (NFC) (#97657)

2024-07-04T20:47:00+00:00

[CommandLine] Avoid ManagedStatic.h include (NFC)

2024-06-21T13:45:17+00:00

The two variables using ManagedStatic that are exported by this
header are not actually used anywhere -- they are used through
SubCommand::getTopLevel() and SubCommand::getAll() instead.
Drop the extern declarations and the include.

[Support] Drop nop conversions of StringRef to StringRef (NFC)

2024-05-17T14:30:58+00:00

Both sides here are known to be of StringRef.

[driver] Make --version show if assertions, etc. are enabled (#87585)

2024-04-05T17:01:09+00:00

It's useful to have some significant build options visible in the
version when investigating problems with a specific compiler artifact.
This makes it easy to see if assertions, expensive checks, sanitizers,
etc. are enabled when checking a compiler version.

Example config line output:
Build configuration: +unoptimized, +assertions, +asan, +ubsan