mfi(4)/mrsas(4): Set sysctl name for driver versions consistently
Instead of printing the driver version over and over again if multiple
controllers are used, set a sysctl name for the used driver version.
Approved by: imp, ziaee
MFC after: 3 days
Differential Revision: https://reviews.freebsd.org/D56110
Bump __FreeBSD_version to 1500509 after linuxkpi changes for DRM 6.12.84
As of this commit, all changes to linuxkpi required by the DRM drivers
from Linux 6.12.84 were committed.
Sponsored by: The FreeBSD Foundation
[clang] teach OpenCL to set the param addrspace before calling CG EmitParmDecl (#184264)
Unfortunately, this still ends up in a slightly awkward place between
Sema and CG, since a few CG phases create implicit parameters (e.g. for
`this`) which also need to be deduced into the correct address space by
Sema. This is intended to be clearly extensible for other targets that
also need this.
Changes the constructor for ImplicitParamDecl to be private again, so
that all users will go through the Create method, by making the object
ctor itself declared `protected` (like all the other VarDecl subtypes).
The memory is later cleaned up by the ASTContext bump allocator, and
since the stack is basically also a bump allocator, is is typically
equally fast. (Reverts 550d13aebbcc03806811a3aa08e674b9b84e08e8)
(If I got my commit stacked extraction right) This should allow removing
the special cases for OpenCL from EmitParmDecl once
https://github.com/llvm/llvm-project/pull/181390 lands, since this
aligns the behavior of that function with the declared intent of each
[7 lines not shown]
[clang][NFC] Reduce one of JSON dump tests (#195026)
#125791 introduced `strict-pack-match` flag for
`ClassTemplateSpecializationDecl`, and covered it with AST dump tests in
`ast-dump-template.cpp`, in both textual and JSON formats. However, JSON
test was generated by a script, which made it overspecified. This PR
extracts the relevant part of ≈9200 lines of FileCheck directives.
[BOLT][AArch64] Add a failing test to demonstrate bug (#194896)
When not in compact-code-model the longjump pass may consider certain
branches in range, but later at JITLink hugify forces them out of range
probably because it aligns hot code at runtime.
NAS-140867 / 27.0.0-BETA.1 / Fix removed methods handling (#18872)
Currently, methods that have `removed_in` set are removed from
corresponding API completely, so we can't call them from our integration
tests. That's not the desired behavior, because we just might have plans
to make them private.
Expand reporting tests
This fixes a schema field name typo for reporting disks
(appears in API docs, but does not change surfaced
reporting.realtime event field names -- typo only was in
docs) in addition to adding explicit testing for internal
utilities as well as validating shape of returned
responses.
