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

[llvm] Use llvm::copy (NFC) (#137470)

2025-04-26T22:50:38+00:00

[ExecutionEngine] Remove unused includes (NFC) (#116749)

2024-11-20T03:41:59+00:00

Identified with misc-include-cleaner.

Fix warnings introduced in #111434 [-Wnontrivial-memaccess]

2024-10-29T05:18:24+00:00

[LLVM] Use {} instead of std::nullopt to initialize empty ArrayRef (#109133)

2024-09-19T15:16:38+00:00

It is almost always simpler to use {} instead of std::nullopt to
initialize an empty ArrayRef. This patch changes all occurrences I could
find in LLVM itself. In future the ArrayRef(std::nullopt_t) constructor
could be deprecated or removed.

[ExecutionEngine] Use range-based for loops (NFC) (#98110)

2024-07-10T07:11:07+00:00

[IR] Add getDataLayout() helpers to Function and GlobalValue (#96919)

2024-06-28T06:36:49+00:00

Similar to https://github.com/llvm/llvm-project/pull/96902, this adds
`getDataLayout()` helpers to Function and GlobalValue, replacing the
current `getParent()->getDataLayout()` pattern.

[llvm] Use SmallString::operator std::string (NFC)

2024-01-20T02:54:11+00:00

[NFC] sentinal -> sentinel

2024-01-16T17:22:06+00:00

[NFC] Remove Type::getInt8PtrTy (#71029)

2023-11-07T16:26:26+00:00

Replace this with PointerType::getUnqual().
Followup to the opaque pointer transition. Fixes an in-code TODO item.

[Interpreter] Add initialization of array members (#66172)

2023-10-20T13:27:11+00:00

Currently, the interpreter does not initialize `undef` constants of
aggregate types correctly (with respect to arrays).
The initialization of the array elements is skipped although it is valid
to directly write to them. Instructions like
`insertvalue {i32, [4 x i32]} undef, i32 1, 1, 2` therefore lead to a
crash.
This is fixed by initializing array values just as fixed-size vectors or
structs.