[compiler-rt][ARM] Optimized single-precision FP comparisons (#179925)
These comparison functions follow the same structure as the
double-precision ones in a prior commit, of a header file containing the
main logic and some entry points varying the construction of the return
value.
In this case, we have provided versions for Thumb1 as well as
Arm/Thumb2.
[clangd] Fix parens suppression in mid-identifier code-completion (#197249)
When completing in the middle of an existing identifier (e.g.
`fo^o<int>(42)`), the next-token check lexes the character immediately
after the cursor, which prevents parens suppression to kick in.
After the fix, we go to the end of the current identifier first and only
then we start lexing for the next token, which handles redundant parens
even when the cursor is mid-identifier.
This also fixes the parens suppression in the replace mode which by
design is used mid-identifier.
Fixes https://github.com/clangd/clangd/issues/387
[AMDGPU][GCNPreRAOptimizations] Reduce BVH premature reuse (#197386)
Add implicit uses to ds_bvh_stack instructions to avoid reuse of VGPRs
allocated to bvh_intersect_ray results prior to ds_bvh_stack. This
reduces likelihood of a premature s_wait_bvhcnt occuring due to partial
reallocation of unused bvh_intersect_ray results registers.
[compiler-rt][ARM] Optimized double-precision FP comparisons (#179924)
The structure of these comparison functions consists of a header file
containing the main code, and several `.S` files that include that
header with different macro definitions, so that they can use the same
procedure to determine the logical comparison result and then just
translate it into a return value in different ways.
net/py-kombu: Switch AWS option from py-boto to py-boto3
devel/py-boto was deleted long ago; kombu has supported boto3 since 4.1.
PR: 288530
Submitted by: James TD Smith <ahktenzero+freebsd at mohorovi.cc>
Firewall: Rules [new] - fix unintended change in filtering logic caused by https://github.com/opnsense/core/commit/c4aefc08f41167b921595cd3f606aadc72b46730
When inspect mode is not selected, only full matches are expected when filtering specific interfaces.
This also means when selecting the inverse of an interface, it automatically belongs to the "floating" group for not being a direct match.
To explain the options a bit better, comments are inserted in the filtereing block.
[AArch64][clang] Improve -mcpu= and -mtune= error messages too
Similar to my previous change improving the error message for
`-march=` in #197441, this changes `-mcpu=` and `-mtune=` arguments
to only report the invalid feature flag, rather than the entire
string.
This is a much clearer error message for the user.
