[MLIR][ACC] Fix -Wunused-variable in dfe7738
There was a variable only used in an assertion which causes warnings in
non-assertions builds. Fix the issue by inlining the variable into the
assertion given it is only used in one place.
[Clang][NFC] Apply Rule of Three to AttrScopedAttrEquivalenceContext (#184905)
Static analysis flagged AttrScopedAttrEquivalenceContext as having a
user defined destructor but not having copy ctor or copy assignment. I
set them as deleted since they are not needed.
[ORC] Refactor some WaitingOnGraph loops into named methods. NFCI. (#184775)
Adds new methods to SuperNode for updating ElemToSuperNodeMap values,
use it to tidy up some loops.
filesystems/gvfs: split and exclude OneDrive option
...until port is updated to 1.58, due to net/msgraph API break:
Run-time dependency msgraph-0.1 found: NO (tried pkgconfig)
meson.build:434:16: ERROR: Dependency "msgraph-0.1" not found, tried pkgconfig
While here, sort OPTIONS_DEFINE
(cherry picked from commit 00646779248e6f9432990e02397ee4a042373c44)
[SYCL] SYCL host kernel launch support for the sycl_kernel_entry_point attribute. (#152403)
The `sycl_kernel_entry_point` attribute facilitates the generation of an
offload kernel entry point function based on the parameters and body
of the attributed function. This change extends the behavior of that
attribute to support integration with a SYCL runtime library through
an interface that communicates symbol names and kernel arguments
for the generated offload kernel entry point functions.
Consider the following function declared with the
`sycl_kernel_entry_point` attribute with a call to this function
occurring in the implementation of a SYCL kernel invocation function
such as `sycl::handler::single_task()`.
```c++
template<typename KernelName, typename KernelType>
[[clang::sycl_kernel_entry_point(KernelName)]]
void kernel_entry_point(KernelType kernel) {
kernel();
}
[49 lines not shown]
[clang-tidy][NFC] Add missing Option tests in `readability` [2/N] (#184708)
This PR adds testcases for untested Options in `readability` module for
better test coverage, specifically:
- `readability-identifier-length`: `IgnoredExceptionVariableNames`,
`IgnoredLoopCounterNames`, `IgnoredParameterNames`,
`MinimumExceptionNameLength`, `MinimumLoopCounterNameLength`,
`MinimumParameterNameLength`, `MinimumVariableNameLength`.
- `readability-magic-numbers`: `IgnoreAllFloatingPointValues`.
- `readability-qualified-auto`: `AddConstToQualified`.
- `readability-redundant-parentheses`: `AllowedDecls`.
- `readability-suspicious-call-argument`: `MinimumIdentifierNameLength`.
- `readability-use-std-min-max`: `IncludeStyle`.
As of AI Usage: Assisted by Gemini 3 and Claude (Writing part of the
testcases and pre-commit reviewing).
Update in preparation for 14.4-RELEASE
- Bump BRANCH to RELEASE
- Add the anticipated RELEASE announcement date
- Set a static __FreeBSD_version
Approved by: re (implicit)
Sponsored by: OpenSats Initiative
lesspipe: Allow zstd to operate on a symlink
By default zstd refuses to operate on symlinks, so for example
`zless /var/crash/vmcore.last.zst` failed to view the uncompressed core
file. Add -f to the zstd command line to allow operation on symlinks.
Reviewed by: delphij
Sponsored by: The FreeBSD Foundation
Differential Revision: https://reviews.freebsd.org/D55101
(cherry picked from commit b4305c90a3be7e1a40b76545b8b761fdbda5c309)
(cherry picked from commit 68125692efacbce537e14ba16ecedff750cccc36)
lesspipe: Allow zstd to operate on a symlink
By default zstd refuses to operate on symlinks, so for example
`zless /var/crash/vmcore.last.zst` failed to view the uncompressed core
file. Add -f to the zstd command line to allow operation on symlinks.
Reviewed by: delphij
Sponsored by: The FreeBSD Foundation
Differential Revision: https://reviews.freebsd.org/D55101
(cherry picked from commit b4305c90a3be7e1a40b76545b8b761fdbda5c309)
lesspipe: Allow zstd to operate on a symlink
By default zstd refuses to operate on symlinks, so for example
`zless /var/crash/vmcore.last.zst` failed to view the uncompressed core
file. Add -f to the zstd command line to allow operation on symlinks.
Reviewed by: delphij
Sponsored by: The FreeBSD Foundation
Differential Revision: https://reviews.freebsd.org/D55101
(cherry picked from commit b4305c90a3be7e1a40b76545b8b761fdbda5c309)
[clang][modules] -Wmodule-import-in-extern-c should not be an error by default (#184530)
Importing a module inside of an `extern "C" {...}` section doesn't have
any effect, i.e. the imported module is not treated as `extern "C"`,
it's built independent of the includer state. The warning is akin to
`-Wconfig-macros`, it's trying to say that the behavior will be
different (and unexpected) when compiling with modules. That doesn't
need to be an error, a warning is enough. As an error, it makes it
difficult to support and test modules in C++ mode while dependencies
still have includes in `extern "C" {...}`.
rdar://171677028
