[Clang][Coroutines] Don't emit fake uses for coroutine parameters (#194690)
Fixes issue: https://github.com/llvm/llvm-project/issues/192351
The combination of coroutines with -fextend-variable-liveness has
resulted in use-after-free, caused by the fact that we insert fake uses
of coroutine parameters at the end of the coroutine. While this is fine
for normal functions, in coroutines these variables are stored in the
coroutine frame, which is freed before the end of the function; this
results in us loading from the deleted frame.
This patch fixes this by no longer emitting fake uses for most coroutine
parameters. Since coroutine parameters will be saved back to the frame
when we suspend, and currently may not be optimized out, fake uses are
not needed in this case, and so by not emitting them we avoid dealing
with the complexity of updating fake uses in the CoroSplit pass. The
exception to this is 'this', which is not saved to the frame.
(cherry picked from commit efb01c1bf558eaaf8ec64e1a54110584e827f21b)
[AArch64][test] Fix use-after-scope in createInstrInfo (#197622)
https://github.com/llvm/llvm-project/pull/183506 revealed a pre-existing
use-after-scope in createInstrInfo (MSan bot:
https://lab.llvm.org/buildbot/#/builders/164/builds/21562 [*]).
This patch fixes the issue by changing the stack-allocated
AArch64Subtarget (which goes out of scope once createInstrInfo()
returns) into heap-allocated, allowing it to be safely stored in the
returned AArch64InstrInfo.
-----
[*] WARNING: MemorySanitizer: use-of-uninitialized-value
#0 0x55555666fabd in
llvm::AArch64InstrInfo::getInstSizeInBytes(llvm::MachineInstr const&)
const
/home/b/sanitizer-x86_64-linux-bootstrap-msan/build/llvm-project/llvm/lib/Target/AArch64/AArch64InstrInfo.cpp:247:5
...
[19 lines not shown]
[AArch64] Keep MMO when converting gather lane to LDRSui. (#197522)
We were losing the MMO when converting the load. Make sure we copy them
over, which apparently alters codegen more than I expected and helps
keep postinc generation after #196305.
databases/leofs: Remove due to obsolescence
LeoFS doesn't have an upstream release in years, and depends on an
obsolete and unsupported version of Erlang.
Approved by: erlang
Sponsored by: SkunkWerks, GmbH
lang/erlang-runtime29: Bump PORTREVISION
Required to ensure that RC-installed versions will upgrade to the final
release.
Fixes: e7938f387cbd0d667723f6d15422ecc62f568259
Sponsored by: SkunkWerks, GmbH
security update to 1.30.1;
- HTTP/2 request injection vulnerability in the ngx_http_proxy_module
(CVE-2026-42926)
- buffer overflow vulnerability in the ngx_http_rewrite_module
(CVE-2026-42945)
- buffer overread vulnerability in the ngx_http_scgi_module and ngx_http_uwsgi_module
(CVE-2026-42946)
- buffer overread vulnerability in the ngx_http_charset_module
(CVE-2026-42934)
- address spoofing vulnerability in HTTP/3
(CVE-2026-40460)
- use-after-free vulnerability in OCSP requests to resolver
(CVE-2026-40701)
[AMDGPU] Remove RCP_IFLAG combine (#197426)
The combine was added in D48569 8 years ago with the aim of preserving
flags, but the current LangRef says the status flags are not observable
in the default FP environment.
The main motivation for this change is to enable scalar float reciprocal
generation v_s_rcp_f32 on newer hardware. There is no v_s_rcp_iflag_f32,
so the combine effectively blocks the selection.
See: pseudo-scalar-transcendental.ll.
misc/swissfileknife: update the port to version 2.0.0.3
- Strip CR symbols from installed documentation files
- Add missing Oxford comma in the port description
Ignored by: portscout :(
