[gsymutil] Fix a warning on systems with 32-bit `off_t` (#189524)
The size of `off_t` isn't specified, so it can be either 32 or 64 bits
depending on the system. In particular, on LLP64 systems like windows
it's generally only 32 bits. This means the `if (StrtabSize >
UINT32_MAX)` check added in #181458 may warn on such systems (Giving
-Wsign-compare).
Given that `FileWriter::tell` (and the underlying `raw_ostream::tell`)
explicitly return `uint64_t`, the simplest fix is to just use the return
type of the function instead of potentially truncating. Since the same
logic applies even where we don't happen to have a warning here, I've
applied this for all of these uses of `off_t`.
lang/go126: Update to 1.26.2
Changes:
go1.26.2 (released 2026-04-07) includes security fixes to the go
command, the compiler, and the archive/tar, crypto/tls, crypto/x509,
html/template, and os packages, as well as bug fixes to the go
command, the go fix command, the compiler, the linker, the runtime,
and the net, net/http, and net/url packages. See the Go 1.26.2
milestone on our issue tracker for details.
PR: 294339
MFH: 2026Q2
(cherry picked from commit 4394f8c204ee51a1da61cb457aa2af0cddaf19c7)
lang/go125: Update to 1.25.9
Changes:
go1.25.9 (released 2026-04-07) includes security fixes to the go
command, the compiler, and the archive/tar, crypto/tls, crypto/x509,
html/template, and os packages, as well as bug fixes to the go
command, the compiler, and the runtime. See the Go 1.25.9 milestone on
our issue tracker for details.
MFH: 2026Q2
(cherry picked from commit 3ee235883c5aaf37f264dbddaa131d5857525260)
Allow passing xtras to safe_set
This allows safe_set to be leveraged in other contexts
where additional chars like '*' or '!' or even '\[\]' need to
be preserved in the result.
[compiler-rt] Address dlvsym not found compilation error when targeting certain platforms (#191444)
#191098 Add some unguarded dlvsym calls. This causes build issues when
targeting certain platforms such as iOS.
This change should restore the original behavior.
[AsmPrinter] Explicitly use EHStreamer type for EHHandlers (#191288)
There is a note here that this causes warnings on some compilers, but it
is unclear what compilers. Clang does not warn on this, and this is the
only compiler that we guarantee to be warning free.
Also update uses of update handle additions to add to the right arrays.
[lldb-dap] Address a race condition in server mode. (#191062)
While running in server mode, multiple clients can be connected at the
same time. In LLDBUtils we had a static mutex that can cause other
clients to hang due to the single static lock.
Instead, I adjusted the logic to take the existing SBMutex as a paremter
and guard that mutex during command handling.
lang/go126: Update to 1.26.2
Changes:
go1.26.2 (released 2026-04-07) includes security fixes to the go
command, the compiler, and the archive/tar, crypto/tls, crypto/x509,
html/template, and os packages, as well as bug fixes to the go
command, the go fix command, the compiler, the linker, the runtime,
and the net, net/http, and net/url packages. See the Go 1.26.2
milestone on our issue tracker for details.
PR: 294339
MFH: 2026Q2
lang/go125: Update to 1.25.9
Changes:
go1.25.9 (released 2026-04-07) includes security fixes to the go
command, the compiler, and the archive/tar, crypto/tls, crypto/x509,
html/template, and os packages, as well as bug fixes to the go
command, the compiler, and the runtime. See the Go 1.25.9 milestone on
our issue tracker for details.
MFH: 2026Q2
[DAGCombiner][GlobalISel] Extract isFusedOp lambda, add FMA contraction test, fix missing isFPExtFoldable check
Extract the duplicated isFusedOp lambda in visitFADDForFMACombine and
visitFSUBForFMACombine into a shared static template function.
Add fma-multiple-uses-contraction.ll test file with baseline CHECK lines
for testing FMA contraction behavior when fmul has multiple uses.
This test will be updated in subsequent patches as contraction prevention
logic is added.
Fix a missing isFPExtFoldable check in GISel's
matchCombineFSubFpExtFMulToFMadOrFMA which could incorrectly fold
fsub(fpext(fmul)) into fma on targets where the fpext is not actually
foldable (e.g., gfx9-generic). This makes GISel consistent with SDAG,
which already checks isFPExtFoldable at all fpext fold sites.
Co-Authored-By: Claude Opus 4.6 <noreply at anthropic.com>
Made-with: Cursor
[LegalizeIntegerTypes] Remove some unnecessary isTypeLegal checks from IntegerExpandSetCCOperands. NFC (#191353)
LHSLo and RHSLo must have the same type, we don't need to check both.
Same for LHSHi and RHSHi.
[SystemZ][z/OS] Remove use of subsections.
HLASM has no notion of subsections. There are several possible solutions
how to deal with this. However,
- using a different section introduces a lot of relocations, which slows
down the binder later
- emitting the PPA1 after the code changes the location which may break
existing tools
The choosen solution is to record the PPA1 data, and emit them at the
end of the assembly into the code section. This solves both issues,
at the expense of having to do some bookkeeping.
This change moves the position of the PPA2, too, but this is less
critical.
