[AMDGPU][SIInsertWaitcnt][NFC] Replace LastFlat array with distinct variables (#185993)
We only seem to be using LastFlat[LOAD_CNT] and LastFlat[DS_CNT] so it
doesn't look like there is a good reason for using an array. Also, we
seem to be operating on all elements of the array while merging, which
is not great.
[TargetLowering] Remove INT_MIN special case from prepareSREMEqFold. (#188653)
If the divisor is INT_MIN, we can still treat it like any other power of
2. We'll fold i32 (seteq (srem X, INT_MIN)) to
(setule (rotr (add (mul X, 1), INT_MIN), 31), 1). Alive2 says this is
correct https://alive2.llvm.org/ce/z/vjzqKk.
The multiply is a NOP, the add toggles the sign bits. The rotate puts
the lowest 31 bits of into the upper 31 bits. The sign bit is now in the
LSB. The compare checks if the upper 31 bits are 0.
srem X, INT_MIN has a remainder of 0 if X is 0 or INT_MIN which is
equivalent to checking if the uppper 31 bits are 0 after the rotate.
I don't think we need to add any constant for power of 2 but toggling
the sign bit like we do now doesn't hurt.
Pull up following revision(s) (requested by hans in ticket #1248):
sys/arch/vax/boot/boot/conf.c: revision 1.19
sys/arch/vax/boot/boot/ra.c: revision 1.23
sys/arch/vax/boot/boot/vaxstand.h: revision 1.12
sys/arch/vax/uba/uba_mainbus.c: revision 1.15
vax/uba: fix detection of CMD CQD-22x MSCP controllers
Certain models of CMD MSCP controllers fail to be detected by uda(4) if
they have been booted from. This failure mode has been introduced in
revision 1.11 of uba_mainbus.c, when scanning for Qbus/Unibus memories
was added. They are deteced fine when NetBSD is booted from any other
device such as over the network.
When NetBSD is booted from a MSCP controller, the boot loader sets up
the Qbus map to provide the controller with a small command/response
ring in memory to be used for I/O. Once the kernel is loaded and uba(4)
is attaching, the Qbus map is cleared while scanning for memories. It
[47 lines not shown]
[Clang] Fixed the behavior of C23 auto when an array type was specified for a `char *` (#189722)
At the time of the implementation of
[N3007](https://www.open-std.org/jtc1/sc22/wg14/www/docs/n3007.htm) in
Clang, when an array type was specified, an error was emitted unless the
deduced type was a `char *`.
After further inspection in the C standard, it turns out that the
inferred type of an `char[]` should be deduced to a `char *`, which
should emit an error if an array type is specified with `auto`.
This now invalidates the following cases:
```c
auto s1[] = "test";
auto s2[4] = "test";
auto s3[5] = "test";
```
Fixes #162694
Pull up the following, requested by kre in ticket #215:
external/public-domain/tz/dist/CONTRIBUTING up to 1.1.1.10
external/public-domain/tz/dist/Makefile up to 1.5
external/public-domain/tz/dist/NEWS up to 1.6
external/public-domain/tz/dist/README up to 1.3
external/public-domain/tz/dist/SECURITY up to 1.1.1.2
external/public-domain/tz/dist/TZDATA_VERSION up to 1.44
external/public-domain/tz/dist/africa up to 1.3
external/public-domain/tz/dist/antarctica up to 1.4
external/public-domain/tz/dist/asia up to 1.16
external/public-domain/tz/dist/australasia up to 1.12
external/public-domain/tz/dist/backzone up to 1.4
external/public-domain/tz/dist/calendars up to 1.1.1.3
external/public-domain/tz/dist/checknow.awk up to 1.4
external/public-domain/tz/dist/etcetera up to 1.4
external/public-domain/tz/dist/europe up to 1.5
external/public-domain/tz/dist/iso3166.tab up to 1.1.1.10
external/public-domain/tz/dist/leap-seconds.list up to 1.11
[11 lines not shown]
[LV] Adjust exit recipe detection to run on early vplan (#183318)
Splitting out some work from #178454; this covers the enums for
early exit loop type (none, readonly, readwrite) and the style
used (readonly with multiple exit blocks, or masking with the
last iteration done in scalar code), along with changing the early
exit recipe detection to suit moving the transform for handling
early exit readwrite loops earlier in the vplan pipeline.
Add tiering API
This commit modifies the truenas API to wrap around tiering design
in the following ways:
A new namespace zfs.tier. will be added. This contains global
configuration for systemwide tiering settings. Parameters include
- enabled: whether to enable tiering. This feature requries changes
to global ZFS behavior and we will have various internal checks
that check this value in datastore extend context methods.
- max_concurrent_jobs: the maximum number of concurrent rewrite
jobs (tier migrations for existing data).
- min_available_space: point in available space for a dataset where
tier migrations will error out.
The namespace will also support APIs for managing and querying
[9 lines not shown]
rust*: Update illumos builds.
rust193's distinfo entry for patch-vendor_openssl-src-300.5.4+3.5.4_src_lib.rs
is incorrect, and rust194's patch to sanity.rs breaks builds, but I've left
those alone.
Pull up following revision(s) (requested by joe in ticket #213):
sys/net/npf/npf_socket.c: revision 1.5
ensure softnet lock is held rather re-locking
If we are about to interact with sockets
we should just ensure that the softnet_lock is held.
Because sockets initializations acquire that lock.
fixes PR kern/60060
