security/doas: Update 6.3p13 => 6.4
Changelog:
- Fix some typos in the documentation.
- Cause doasedit to better handle shell variables and find the best
text editor for altering files.
Improve port:
- Move BINMODE=4755 to plist: "@(,,4755) bin/doas" - BINMODE is applied
universally (to all programs and scripts). This means helper scripts
like doasedit, which are meant to be run as a regular user, were also
installed as setuid. This is a potential security issue.
- Move plist to file.
- Add "@sample" for "etc/doas.conf.sample".
PR: 293628
Sponsored by: UNIS Labs
MFH: 2026Q2
Co-authored-by: Vladimir Druzenko <vvd at FreeBSD.org>
[2 lines not shown]
security/doas: Update 6.3p13 => 6.4
Changelog:
- Fix some typos in the documentation.
- Cause doasedit to better handle shell variables and find the best
text editor for altering files.
Improve port:
- Move BINMODE=4755 to plist: "@(,,4755) bin/doas" - BINMODE is applied
universally (to all programs and scripts). This means helper scripts
like doasedit, which are meant to be run as a regular user, were also
installed as setuid. This is a potential security issue.
- Move plist to file.
- Add "@sample" for "etc/doas.conf.sample".
PR: 293628
Sponsored by: UNIS Labs
MFH: 2026Q2
Co-authored-by: Vladimir Druzenko <vvd at FreeBSD.org>
[CodeGen] Move rollback capabilities outside of the rematerializer (#184341)
The rematerializer implements support for rolling back
rematerializations by modifying MIs that should normally be deleted in
an attempt to make them "transparent" to other analyses. This involves:
1. setting their opcode to DBG_VALUE and
2. setting their read register operands to the sentinel register.
This approach has several drawbacks.
1. It forces the rematerializer to support tracking these "dead MIs"
(even if support is optional, these data-structures have to exist).
2. It is not actually clear whether this mechanism will interact well
with all other analyses. This is an issue since the intent of the
rematerializer is to be usable in as many contexts as possible.
3. In practice, it has shown itself to be relatively error-prone.
This commit removes rollback support from the rematerializer and moves
[5 lines not shown]
[lldb][NativePDB] Handle `S_DEFRANGE_REGISTER_REL_INDIR` (#190336)
Since #189401, LLVM and Clang generate `S_DEFRANGE_REGISTER_REL_INDIR`
for indirect locations. This adds support in LLDB.
The offset added after dereferencing is signed here - unlike in
`S_REGREL32_INDIR` (at least that's the assumption). So I updated
`MakeRegisterBasedIndirectLocationExpressionInternal` to handle the
signedness. This is the reason the MSVC test was changed here.
I didn't find a test case where LLVM emits the record with the `VFRAME`
register. Other than that, the clang test is similar to the MSVC one
except that the locations are slightly different.
[VFS] Guard against null key/value nodes when parsing YAML overlay (#190506)
When a VFS overlay YAML file contains malformed content such as tabs,
the YAML parser can produce KeyValueNode entries where `getKey` returns
nullptr. The VFS overlay parser then passes the nullptr to
`parseScalarString`, which then calls dyn_cast.
Switch to `dyn_cast_if_present` for the above callsites and a few more.
[Hexagon] Pass -pie to linker when PIE is the toolchain default (#189723)
The Hexagon driver only checked for an explicit -pie flag when
constructing the link command, ignoring the toolchain's PIE default. For
linux-musl targets, isPIEDefault() returns true (via the Linux toolchain
base class), so the compiler generates PIC/PIE code (-pic-level 2
-pic-is-pie) but the linker never received -pie.
This mismatch caused LTO failures: without -pie the linker sets
Reloc::Static for the LTO backend, which generates GP-relative
(small-data) references that lld cannot resolve.
Use hasFlag() to respect the toolchain default, and guard the -pie
emission against -shared and -r (relocatable) modes.
AMDGPU: Use SmallSet for VOPD scalar reg tracking
Use SmallSet instead of SmallVector for UniqueScalarRegs.
VCC_LO was pushed without uniqueness check, so when both
components used VCC implicitly it was counted twice,
rejecting valid VOPD pairings.
Co-Authored-By: Claude Opus 4.6 <noreply at anthropic.com>
[AMDGPU] Update vop3-literal.s to use fake16 on gfx1250. NFC (#190243)
16-bit instructions there are in fake16 mode and shall also be
compatible with older targets. The purpose of the test is to
check literals, so fake16 or real16 is not important.
[TargetLowering] Speculative fix for a non-determinism issue between different compilers. (#190219)
The evaluation order of function arguments is unspecified by the C++
standard. We had two getNode calls as function arguments which causes
the nodes to be created in a different order depending on the compiler
used. This patch moves them to their own variables to ensure they are
called in the same order on all compilers.
Possible fix for #190148.
(cherry picked from commit e2e5db840109e9a5d5bb190fcae350161a6e5481)
[flang][OpenMP] Implement checks for rectangular loops
Detect non-rectangular loops, emit diagnostic messages when the construct
requires that the affected loops are rectangular. Delete similar checks
from resolve-directive.cpp.
Issue: https://github.com/llvm/llvm-project/issues/185287
[clang-repl] Use canonical types in QualTypeToString (#190528)
Use the canonical type when generating type strings to ensure sugared
(e.g. `AutoType`, `DecltypeType`) are resolved before calling
getFullyQualifiedType.
This will revert a few commits that were added to fix these assertions.
---------
Co-authored-by: Harald van Dijk <hdijk at accesssoftek.com>
(cherry picked from commit ba286040c95ea7a15673d6a7f731dc090ffe1fde)
[clang] Fix issues with const/pure on varargs function. (#190252)
There are two related issues here. On the declaration/definition side,
we need to make sure the markings are conservative. Then on the caller
side, we need to make sure we don't access parameters that don't exist.
Fixes #187535.
(cherry picked from commit 9471fabf8ab15b1dc03834a1b7b7d20a038a4656)
AMDGPU: Validate VOPD physical src regs against operand RC
Replace isVGPR checks with matchesVOPDOperandRC that
validates physical source registers against the actual
VOPD combined instruction's operand register classes.
[Scheduler][NFC] Don't use set to track visited nodes (#190480)
The visited set can grow rather large and we can use an unused field in
SDNode to store the same information without the use of a hash set.
This improves compile times: stage2-O3 -0.14%.
