[lldb][Windows] use Unicode path limit (#206060)
`MAX_PATH` is defined as `260`. `PosixApi.h` already defines `PATH_MAX`
as `32,768` characters which is the max path limit for Unicode paths on
Windows.
Use this in lldb on Windows to avoid path truncation.
[X86] Mark AsmPrinter Module Passes as Required (#206164)
This won't impact them working on optnone functions, but could impact
whether or not they get called in opt-bisect, which would be wrong.
Merge tag 'thermal-7.2-rc1-2' of git://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm
Pull thermal control fixes from Rafael Wysocki:
"These fix a failure path in an Intel thermal driver and prevent
thermal testing module code from being executed after it has been
freed:
- Fix dangling resources on thermal_throttle_online() failure in the
Intel thermal_throttle driver (Ricardo Neri)
- Eliminate a possibility of running thermal testing module code
after that module has been removed (Rafael Wysocki)"
* tag 'thermal-7.2-rc1-2' of git://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm:
thermal: testing: zone: Flush work items during cleanup
thermal: intel: Fix dangling resources on thermal_throttle_online() failure
[flang][OpenMP] Support lowering of metadirective (part 3)
Enable metadirective lowering for loop-associated variants such as
`do`, `simd`, `parallel do`, and `do simd`.
When a metadirective resolves to a loop-associated directive, the
associated DO construct is made available to the selected variant so
existing OpenMP loop lowering can process it. Standalone metadirectives
use the following sibling DO evaluation, while begin/end metadirectives
use the first substantive nested evaluation from the metadirective block.
For example, when the `vendor(llvm)` selector matches:
!$omp metadirective when(implementation={vendor(llvm)}: parallel do)
do i = 1, n
y(i) = a*x(i) + y(i)
end do
the selected `parallel do` variant is lowered with the DO loop that
[66 lines not shown]
fdp-primer: Mention that .po files are generated nightly
There is no need to generate the .po files manually as they are
generated every night. Describe this fact in the PO translations
chapter.
PR: 295901
Event: Halifax Hackathon 202606
Location: Back in my old chair
[libc++] Fix instantiation of incomplete type when evaluating tuple comparisons (#204679)
Instantiating std::tuple<T...> in C++23 and later would require
computing tuple_size_v of the tuple type itself, because the
hidden-friend operator<=> and analogous comparison operators query it
for its return type. That can lead to a hard error if instantiating
tuple_size requires the type to be complete.
This patch resolves that problem by refactoring the metaprogramming
around these comparison operators. As a side effect, this should also be
slightly more efficient at compile-time because we don't cause the
instantiation of tuple_element for the current tuple.
rdar://179086119
[RISCV] Ignore Tune Features for Inlining (#205940)
Using the new InlineBehavior field of SubtargetFeature, ensure that
RISC-V's tuning related features do not prevent inlining.
Architecture features still prevent inlining.
Merge tag 'pm-7.2-rc1-2' of git://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm
Pull power management fixes from Rafael Wysocki:
"These fix the schedutil cpufreq governor and drop a bogus warning
from the cpuidle core:
- Remove a misguided warning along with an inaccurate comment
next to it from the cpuidle core (Rafael Wysocki)
- Clear need_freq_update as appropriate in the .adjust_perf()
path of the schedutil cpufreq governor to avoid calling
cpufreq_driver_adjust_perf() unnecessarily on every scheduler
utilization update (Zhongqiu Han)"
* tag 'pm-7.2-rc1-2' of git://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm:
cpuidle: Allow exit latency to exceed target residency
cpufreq: schedutil: Fix uncleared need_freq_update on the .adjust_perf() path
[Hexagon] Add XQFloat code generation and post-RA QFP handling (#198902)
Introduce two new passes for the Hexagon HVX floating-point pipeline,
targeting v79+ where QFloat (qf16/qf32) is the native HVX FP format.
HexagonXQFloatGenerator lowers IEEE-754 HVX floating-point sequences
(sf/hf) to native QFloat (qf16/qf32) operations. QFloat instructions are
faster and more power-efficient than their IEEE counterparts, with
optional accuracy trade-offs. The pass exposes four modes:
* Strict IEEE-754 compliant
* IEEE-754 compliant (extended dynamic range and subnormal precision, no
IEEE-754 overflow handling)
* Lossy subnormals
* Legacy
HexagonPostRAHandleQFP runs after register allocation and corrects the
spill/refill paths. QFloat operands carry four extra precision bits that
are silently dropped if the value passes through a spill slot or a
[6 lines not shown]
[lldb] Move Diagnostics from Utility to Core (NFC) (#206152)
Nothing in the Utility or Host layers uses Diagnostics. Its only callers
are Debugger (the always-on log feeder), SBDebugger, and the
SystemInitializerCommon lifecycle. Those all live in Core or above. The
header depends only on Utility primitives (FileSpec, Log, Error), and
lldbInitialization already links lldbCore, so the move adds no new link
dependency anywhere.
Relocating it to Core lets Diagnostics reach Debugger, Target,
CommandInterpreter, and Host, which simplifies an upcoming change that
collect a richer diagnostics bundle (statistics, command snapshots,
invocation, etc) and allows us to implement that directly in the
Diagnostics class.
[libc] add shared multf3 builtin (#205670)
Re-exposes LLVM-libc's `__multf3` as `shared::multf3` for reuse by
compiler-rt's builtins.
Stacked change - merge these first:
- #200094
- #205669
Part of #197824
---------
Co-authored-by: Muhammad Bassiouni <60100307+bassiounix at users.noreply.github.com>
sysutils/py-salt: mark as BROKEN with python-3.12+
The port will build, but not run, with Python 3.12 or later.
PR: 296290
Reported by: js
MFH: 2026Q2
Approved by: krion (maintainer)
Sponsored by: ConnectWise
[Flang][OpenMP] readd enable-delayed-privatization-staging for implic… (#204466)
…t firstprivate
In e57ebfdaefa7c2ea660878984cfe5c739f626d6b the flag
enableDelayedPrivatizationStaging was removed, enabling
Delayed Privatization for firstprivate on OpenMP target regions,
this resulted in regressions for implicit firstprivate tests:
This commit readds enableDelayedPrivatizationStaging flag for the implicit
case and also guards the explicit change via
`enableDelayedPrivatization` instead of enableDelayedPrivatizationStaging.
[X86] Add target verifier
Add an X86 TargetVerify and register it by triple so the
TargetVerifierPass dispatches to it for X86 modules. It performs no
checks yet; the subtarget-dependent checks are added in a follow-up.
fdp-primer: Include context in the git format-patch for users to use
The quick start section did not instruct the reader to include context
in the git format-patch example. This is not ideal as it makes reviewing
easier. Include this information with a bit of explanation below it.
Event: Halifax Hackathon 202606
Location: A different chair than obiwac's
Reviewed by: lwhsu
Differential Revision: https://reviews.freebsd.org/D57891
Merge tag 'acpi-7.2-rc1-2' of git://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm
Pull ACPI support fixes and cleanups from Rafael Wysocki:
"These fix assorted issues and do cleanups in the ACPI support code,
which includes a fix for tools build breakage related to strncpy()
removal:
- Unbreak ACPICA tools builds after switching over to using
strscpy_pad() that is kernel-specific (Rafael Wysocki)
- Fix module parameter file paths in comments in the ACPI code
managing the general sysfs attributes (Zenghui Yu)
- Update kerneldoc comments in the ACPI resource management code to
follow the common style (Andy Shevchenko)
- Fix inverted interface check in ipmi_bmc_gone() that may cause ACPI
IPMI interfaces to be mishandled (Xu Rao)
[9 lines not shown]
18178 Makefile.master: .cc.a should PROCESS_COMMENT first, then AR
Reviewed by: Jason King <jason.brian.king+illumos at gmail.com>
Reviewed by: Bill Sommerfeld <sommerfeld at hamachi.org>
Approved by: Dan McDonald <danmcd at edgecast.io>
