[NVPTX] Implement llvm.fptrunc.round intrinsic (#223720)
This patch implements hardware-dependent selection for
`llvm.fptrunc.round`.
`round.tonearest` mode is canonicalized to `fpround`, and so is
supported on all
hardware. Other rounding modes are conditionally supported depending on
the SM
and PTX version e.g. bf16 support requires sm80 for rz and sm90 for rm
or rp.
This also adds direct conversions between bfloat and half, e.g.
```
llvm.fptrunc.round.f16.f32 (fpextend x), "round.down"
```
will select `cvt.rm.f16.bf16` on sm90+, or emit a diagnostic.
Assisted-by: GPT-6 Astra
[X86][CostModel] Price predicate mask-expansion fanout for wide predicated ops (#201666)
Teach the X86 TTI cost model to price the *predicate mask-expansion
fanout* of wide predicated operations. When a masked memory op,
gather/scatter, or select produces its predicate as a compact `<N x i1>`
but the data type legalizes into more register parts than that
predicate, codegen must materialize a sub-mask for every extra data part
— a `kshiftr` out of the k-register on AVX-512, or a vector
unpack/sign-extend on SSE/AVX. The per-part cost tables price these ops
linearly in data parts and miss this fanout.
[debuginfo] Add DW_AT_type support to DW_TAG_string_type DIEs (1 of 3) (#217419)
The DWARF spec allows for the DW_TAG_string_type DIE to contain a
DW_AT_type attribute which can be helpful for supporting non-ASCII
character types in a debugger. This requires adding a DIType member to
DIStringType in LLVM IR, and propagating it to the DWARF generator in
the backend. This is part 1 of 3 to add support for this to flang (Issue
#95440)
[clang] Fix thread_local incorrectly treated as tentative definition (#219780)
Fixes #217636.
In C23 (6.9.3p1-2), a file-scope declaration with `thread_local` is a
definition and is excluded from tentative definitions. Clang classified
such
declarations as tentative, so `thread_local int x; thread_local int x;`
was
accepted.
In C23 and later, `VarDecl::isThisDeclarationADefinition` no longer
returns
`TentativeDefinition` for file-scope thread-local variables, and the C
path of
`MergeVarDecl` now diagnoses a redefinition when a thread-local
definition
follows a previous definition. Earlier language modes keep the old
behavior,
[2 lines not shown]
[RISCV][compiler-rt] Asm funcs should be hidden (#226633)
The C builtins are built with `-fvisibility=hidden` when that option is
available, as the builtins are expected to be statically linked and not
called across shared library boundaries.
Before this change, the assembly-written builtin implementations were
declared with STV_DEFAULT visibility, meaning they would be visible
across shared library boundaries. This change moves them to being
declared as STV_HIDDEN to fix this issue.
In particular, the save/restore routines are not normal functions and
cannot be called via a PLT, so this fixes a bug there, and also applies
it to the assembly multiply routine.
[SDPatternMatch] Add m_Node and m_SpecificOpc that take opcode from template argument (#228626)
In most cases, `m_Node` and `m_SpecificOpc` is checking against a fixed
opcode. By taking the opcode it is comparing against from a template
argument, we can guarantee that opcode comparison will be trivial, even
in debug builds. This could potentially improve the compilation time in
the long run.
devel/py-cysignals: use USE_PYTHON=autoplist
Fixes packaging with free-threaded Python.
Also specify USE_PYTHON=pytest instead of USES=pytest
PR: 299133
Approved by: thierry (maintainer)
devel/py-cysignals: use USE_PYTHON=autoplist
Fixes packaging with free-threaded Python.
Also specify USE_PYTHON=pytest instead of USES=pytest
PR: 299133
Approved by: thierry (maintainer)
[lldb] Print the output of failed attempts of flaky tests (#229483)
This patch adds a mechanism to log the output of the failed tries of a
flaky test which ended up passing after multiple attempts.
AMDGPU: Select region address space loads and stores
Fix the annoying asymmetry where we handle local and region for some atomics
but not the full suite of operations. I run into this about once per year and
want to be done with it.
The ugly bits here are to deal with the fact that it appears m0 still requires
initialization in gfx9+. It was simpler to handle the true16 case by
preprocessing the selection to a 32-bit extload as the load truly is, and go
through the ordinary m0 gluing.
Co-authored-by: Claude Opus 5.5 <noreply at anthropic.com>
python.mk: introduce PYTHON_DISABLE_BYTECODE
This is a user variable to allow Python ports to not compile and
include bytecode. For this setting to take effect on existing
packages, rebuilds are required. Ports themselves must not set this
variable.
python.mk: introduce PYTHON_DISABLE_BYTECODE
This is a user variable to allow Python ports to not compile and
include bytecode. For this setting to take effect on existing
packages, rebuilds are required. Ports themselves must not set this
variable.
[llvm][vfs] Add FileSystem::getDirectoryContentRealSources (#216889)
Add a way to ask a VFS which locations in an underlying file system
contribute to enumerating a directory.
This is to support reporting directory dependencies to build systems for
external directories that have their content iterated over.
Assisted-by: Claude Code: opus-5
[NFC][TSan] Remove nullptr location placeholders in ScopedReport (#228825)
#151120 introduced AddedLocationAddr and nullptr placeholders in
ReportDesc::locs when deferring SymbolizeData(addr) from
ScopedReport::AddLocation to SymbolizeStackElems(). Because
SymbolizeData is only reached at the end of AddLocation (which is called
at most once per report), preserving placeholder indices in
ReportDesc::locs is unnecessary.
Replace AddedLocationAddr and nullptr placeholders in ReportDesc::locs
with Vector<uptr> loc_addrs, and append symbolized data locations in
ScopedReport::SymbolizeStackElems() without needing a compaction pass.
Assisted-by: Gemini
bsnmp: validate the lower bound of error_index in responses
Check if the response's error_index is within a sane interval.
Otherwise, a rogue peer could crash us.
PR: 298222
Reported by: Robert Morris
Reviewed by: markj
Discussed with: secteam (markj)
MFC after: 2 weeks
Analyzed with: Claude Code Opus 5
(cherry picked from commit 296e3fd54ca8972fa6696974097a2f2705f8dfc4)
bsnmp: validate the lower bound of error_index in responses
Check if the response's error_index is within a sane interval.
Otherwise, a rogue peer could crash us.
PR: 298222
Reported by: Robert Morris
Reviewed by: markj
Discussed with: secteam (markj)
MFC after: 2 weeks
Analyzed with: Claude Code Opus 5
(cherry picked from commit 296e3fd54ca8972fa6696974097a2f2705f8dfc4)
[CIR] Fix a crash on void{} and void conditional expressions
CIR was crashing on `void{}` and on conditionals like
`c ? void() : void()`. This change fixes that by returning a null value
for these void expressions, which is how CIR already handles `void()`
and casts to void. `VisitInitListExpr` now returns early for `void{}`.
When both arms of a cheap conditional are void, we evaluate them and
return a null value instead of building a select, the same as classic
codegen.
Assisted-by: Claude Code / Claude Opus 5.5
