InstCombine: Handle fsub in SimplifyDemandedFPClass (#175852)
alive2 fails on some of the tests, but this is due to existing
folds in instsimplify and
https://github.com/AliveToolkit/alive2/issues/1273
Merge tag 'kbuild-fixes-6.19-2' of git://git.kernel.org/pub/scm/linux/kernel/git/kbuild/linux
Pull kbuild fixes from Nicolas Schier:
- Reduce possible complications when cross-compiling by increasing use
of ${NM} in check-function-names.sh
- Fix static linking of nconf
* tag 'kbuild-fixes-6.19-2' of git://git.kernel.org/pub/scm/linux/kernel/git/kbuild/linux:
kconfig: fix static linking of nconf
kbuild: prefer ${NM} in check-function-names.sh
x11/xscreensaver: Update 6.13 => 6.14
New savers in this release are actually shell scripts, however still
being stripped which fails. Work around this by performing stripping
manually on the files are known or detected as binary executables.
While here, deduplicate MASTER_SITES/WWW--those are the same. Also,
download will go through HTTPS now.
Changelog:
* Added the ability to run shadertoy.com programs as screen savers.
* New shader-based savers: alienbeacon, batteredplanet, elementalring,
fluxcore, gimbalharmonics, hexplasma, logarithmiccircles, neongravity,
neontriangulator, protophore, selfreflect, skyline, stardome,
starnest, stripeytorus, synthwavecity, topologica and truchetzoom.
* Better label wrapping in carousel and photopile.
* Fixed glslideshow preferences and title display.
* X11: Decrufted PAM, including /etc/pam.d/xscreensaver.
* macOS: Sparkle 2.8.
[4 lines not shown]
InstCombine: Fold known-qnan results to a literal nan
Previously we only considered fcNan to fold to qnan for canonicalizing
results, ignoring the simpler case where we know the nan is already
quiet.
AMDGPU: Disable scheduler mfma rewrite stage by default for now (#177624)
Currently generating an excess number of copies. Turning it off to avoid
churn for other developers.
[libc++] Automatically detect the libc++ hardening mode from the test suite (#172505)
This prevents hardcoding the hardening mode via compiler flags, and
allows testing what the default hardening mode is on platforms that set
it to something that isn't `none`. Otherwise, a platform setting a
default (which is done via -DLIBCXX_HARDENING_MODE=mode at CMake
configuration time) would end up passing `-D_LIBCPP_HARDENING_MODE=mode`
to the compiler, which does not allow checking what the default mode is.