llvm-project.git/lldb/source/Utility/ArchSpec.cpp, branch users/nico/python-2

[lldb] Remove unused local variables (NFC) (#138457)

2025-05-04T18:56:22+00:00

Add MachO RISC-V CPU type and CPU subtype to llvm & lldb (#136785)

2025-04-23T18:03:40+00:00

Add the enum values for MachO RISC-V CPU type and CPU subtype to
llvm and use in LLDB's ArchSpec.

[lldb] [darwin] Upstream a few DriverKit cases (#126604)

2025-02-10T22:49:53+00:00

A DriverKit process is a kernel extension that runs in userland, instead
of running in the kernel address space/priv levels, they've been around
a couple of years. From lldb's perspective a DriverKit process is no
different from any other userland level process, but it has a different
Triple so we need to handle those cases in the lldb codebase. Some of
the DriverKit triple handling had been upstreamed to llvm-project, but I
noticed a few cases that had not yet. Cleaning that up.

[lldb] Add amd64 ArchSpec (#122533)

2025-01-13T19:37:06+00:00

amd64 is used on OpenBSD.

[lldb] Add armv7a and armv8a ArchSpecs (#106433)

2024-08-29T17:16:17+00:00

armv7a and armv8a are common names for the application subarch for arm.

These names in particular are used in ChromeOS, Android, and a few other
known applications. In ChromeOS, we encountered a bug where armv7a arch
was not recognised and segfaulted when starting an executable on an
arm32 device.

Google Issue Tracker:
https://issuetracker.google.com/361414339

[lldb][AIX] Updating XCOFF,PPC entry in LLDB ArchSpec (#105523)

2024-08-22T08:56:49+00:00

This PR is in reference to porting LLDB on AIX.

Link to discussions on llvm discourse and github:

1. https://discourse.llvm.org/t/port-lldb-to-ibm-aix/80640
2. #101657 

The complete changes for porting are present in this draft PR:
#102601 

The changes in this PR are intended to update the Architecture entry for
LLDB with XCOFF,PPC.

1. Added new ArchitectureType `eArchTypeXCOFF`
2. Added a new `ArchDefinitionEntry g_xcoff_arch_entries[]`
3. Added a new case for `XCOFF in ArchSpec::SetArchitecture(..)`
4. Updated `ArchDefinition *g_arch_definitions[]`

Replace ArchSpec::PiecewiseCompare() with Triple::operator==()

2024-02-26T17:57:07+00:00

Looking ast the definition of both functions this is *almost* an NFC
change, except that Triple also looks at the SubArch (important) and
ObjectFormat (less so).

This fixes a bug that only manifests with how Xcode uses the SBAPI to
attach to a process by name: it guesses the architecture based on the
system. If the system is arm64 and the Process is arm64e Target fails
to update the triple because it deemed the two to be equivalent.

rdar://123338218

Revert "Replace ArchSpec::PiecewiseCompare() with Triple::operator==()"

2024-02-23T23:26:14+00:00

This reverts commit 5e6bed8c0ea2f7fe380127763c8f753adae0fc1b while investigating the bots.

Replace ArchSpec::PiecewiseCompare() with Triple::operator==() (#82804)

2024-02-23T22:00:15+00:00

Looking ast the definition of both functions this is *almost* an NFC
change, except that Triple also looks at the SubArch (important) and
ObjectFormat (less so).

This fixes a bug that only manifests with how Xcode uses the SBAPI to
attach to a process by name: it guesses the architecture based on the
system. If the system is arm64 and the Process is arm64e Target fails to
update the triple because it deemed the two to be equivalent.

rdar://123338218

[lldb] Remove distribution_id from ArchSpec

2023-05-03T17:30:42+00:00

The qHostInfo packet in the gdb-remote communication protocol specifies
that distribution_id can be set, so lldb handles that. But we store that
in the ArchSpec representing the "Host" platform (whatever platform the
debug server is running on). This field is otherwise unused in ArchSpec,
so it would be a lot easier if we stored that information at the
gdb-remote communication layer.

Sidenote: The distribution_id field is currently unused but I did not
want to remove it in case some folks found it useful (e.g. in downstream
forks).

Differential Revision: https://reviews.llvm.org/D149697