x11/nvidia-driver{-devel}, x11/nvidia-kmod{-devel}, x11/linux-nvidia-libs{-devel}, graphics/nvidia-drm*-kmod{-devel}, x11/nvidia-settings, x11/nvidia-xconfig: Update to 620.70.06
Update to latest Production Branch of drivers 620.70.06:
https://www.nvidia.com/en-us/drivers/details/283868/
Linux counterparts for x11/linux-nvidia-libs:
https://www.nvidia.com/en-us/drivers/details/283867/
As this version is newer than exisitng New Feature Branch (NFB)
of drivers, update -devel variants to the same version, too.
Additional note:
Starting from 615 series of drivers, possibly vtys before invoking
whichever of X11 or Wayland shifts screen downward with about
half character-based line, causing command prompt at the bottom
become hard to read.
Once X11 (tested only for xorg) or Wayland starts, it would be
fixed (on exitting X11 / Wayland or switching to vty from X11/
[18 lines not shown]
AArch64: Use the DAG's libcall info (#239895)
Use the analysis libcall info instead of the static copy in
TargetLowering, which will eventually be removed.
Co-authored-by: Claude Opus 5.5 <noreply at anthropic.com>
BPF: Stop lowering unwinding through nonexistent unwinder calls
BPF borrowed the DWARF EH pipeline in an unsound way. DwarfEHPrepare
turned resume into a call of _Unwind_Resume, which will never be
linked in. BPFUnwindLower later replaced it, and calls of
_Unwind_RaiseException, by matching callee names after register
allocation. This fixes the pass pipeline relying on these transient
calls to phantom functions.
Instead add an invokable llvm.bpf.unwind.exit intrinsic, similar to
wasm's throw intrinsics. BPFUnwindPrepare replaces resume with it so
no impossible call to _Unwind_Resume reaches selection.
The intrinsic selects to a pseudo which BPFUnwindLower turns into
either unwind_exit or a branch to the landing pad when invoked. The
pseudo clobbers nothing, so register allocation can be more aggressive
than when the function looked like an ordinary call.
Co-authored-by: Claude Opus 5.5 <noreply at anthropic.com>
security/openssh-portable: Fix build on 14.x
This fixes the build where blacklistd+hpn are used.
(cherry picked from commit 369256b446234a7fbf9f2d33fbcd19b34488a158)
[clang][Sema] Recheck array size once the element type is complete (#219817)
Fixes #213855
`BuildArrayType` can't check an array's byte size when the element type
is still incomplete, for example an array of a class template
specialization that hasn't been instantiated yet. Nothing rechecked it
afterwards, so a `~2^67` byte array type survived as a valid field and
the first size query asserted in `getTypeInfoImpl`.
`RequireCompleteType` now checks the size of a constant array once it is
complete, using the same limit as `BuildArrayType`. The error reports
bytes (new `err_array_size_too_large`) since the element count was
already accepted. Uninitialized variable definitions now require the
whole array type to be complete rather than just the base element type,
as initialized ones already do.
LLM tools were used for this contribution. I've reviewed, built, and
tested the change myself before pushing to GitHub.
X86: Remove clearKillFlags call in X86FlagsCopyLowering (#239893)
Kill flags on physical registers here are either never set by the time
this code runs or are on reserved or constant registers where they
carry no information.
Co-authored-by: Claude Opus 5.5 <noreply at anthropic.com>
[libc++] Implement ADL tests for std::expected (#236608)
Resolves #105307
- LWG3973: `std::expected`'s monadic operations use `this->__val()`
rather than `**this`, so they are already ADL-proof. Added tests to
ensure an ADL-found `operator*` is never selected.
Resolves #171310
- LWG4015: Nothing to do but considered completed together with
`optional<T&>`. It fixes the const overloads of `std::optional`'s
monadic operations from LWG3973's exposition; libc++ uses `value()`
instead of a pointer so the issue is not present.
---------
Co-authored-by: A. Jiang <de34 at live.cn>
BPF: Register the unwind passes (#239891)
Give BPFUnwindPrepare and BPFUnwindLower names, so that tests can stop
after them or run them on MIR.
Co-authored-by: Claude Opus 5.5 <noreply at anthropic.com>
CodeGen: Stop using TargetLowering's libcall info in PreISelIntrinsicLowering
The TargetLowering copy of RuntimeLibcallsInfo should be deleted and
only the analysis should be used.
Co-authored-by: Claude Opus 5.5 <noreply at anthropic.com>
