* String routine changes
  * Added AArch64 ILP32 ABI support.
  * Fixed SVE strnlen return value.
  * Added MTE related __mtag_tag_region.
  * Added MTE related __mtag_tag_zero_region.
  * Minor code cleanups.

Scripted copyright year updates based on git committer date.

Add optimized __mtag_tag_zero_region(dst, len) operation to AOR. It tags
the memory according to the tag of the dst pointer then memsets it to 0
and returns dst. It requires MTE support. The memory remains untagged if
tagging is not enabled for it. The dst must be 16 bytes aligned and len
must be a multiple of 16.

Similar to __mtag_tag_region, but uses the zeroing instructions.

Add optimized __mtag_tag_region(dst, len) operation to AOR. It tags the
given memory region according to the tag of the dst pointer and returns
dst. It requires MTE support. The memory remains untagged if tagging is
not enabled for it. The dst must be 16 bytes aligned and len must be a
multiple of 16.

Cleanup spurious .text and .arch. Use ENTRY rather than ENTRY_ALIGN.

The error report was copied from the seekchar test above,
and needs adjustment to match the gating IF.

There were nops before the beginning of the function to place
the main loop on a 64-byte boundary, but the addition of BTI
and instructions for ILP32 has corrupted that.

As per review, drop 64-byte alignment entirely, and use the
default 16-byte alignment from ENTRY.

These nops were placed to align code to 16-byte boundaries,
but then the addition of BTI and ILP32 has corrupted that.

The comment on the eos-not-found path says that it is
returning the max string length, but it actually uses
the current string length.  This results in returned
values larger than the expected value.

This adds sanitization of padding bits for pointers and size_t types as
required by ARM aapcs64 for the AArch64 ILP32 ABI.

* New math routines
  * Scalar erff and erf using fma.

The code relied on the final x + c*x to be done via an fma, otherwise
the intermediate c*x could underflow for tiny (almost subnormal) x.

Use explicit fmaf like elsewhere (this code is not expected to be
fast when fma is not inlined, but at least it should be correct).

erf has larger than 1 ULP errors in directed rounding modes,
increase the error threshold to 1.4 ULP in the test script.

Only tested in round-to-nearest mode. The expected worst case error
is 1.01 ULP near x=1.25.  Benchmarked over random x in [-6,6] and
can increase performance by > 2x (> 3.5x for throughput) on big ooo
cores compared to the implementation in glibc 2.28.

Includes data for erfc too, but this patch only adds erf.

Make the formatting consistent with other copyright notices.
(This helps me doing automatic license header checks.)

This was incorrect in the previous commit.

In round-to-nearest mode the maximum error is 1.09 ULP.

Compared to glibc-2.28 erff: throughput is about 2.2x better,
latency is about 1.5x better on some AArch64 cores (on random
input in [-4,4]).

There are further optimization and quality improvement opportunities.

* Bug fixes
  * strcmp-mte nul check
  * strncmp-mte with large size
  * arm memcpy with large size (CVE-2020-6096)
* String routines performance improvements
  * strlen
  * memmove with backward copy
* Benchmarking code for strings and memory routines
  * strlen

Add benchmarking of forward and backward unaligned memmoves.

On some microarchitectures performance of the backwards memmove improves
if the stores use STR with decreasing addresses.

This fix is similar to the one done one glibc (beea361050).

Optimize strlen using a mix of scalar and SIMD code. On modern micro
architectures large strings are 55% faster than the current version,
and 35% faster than strlen-mte.  On the random strlen benchmark the
speedup is 3.4% and 40% respectively.

Add strlen benchmark with a random latency and small/medium throughput tests.

If limit is near SIZE_MAX it can overflow in the mutually aligned path.
Fix this by clamping limit to SIZE_MAX.

Improve the previous fix - if a string is immediately preceded by a NUL byte
and the first byte is 0x1, it may be confused by the NUL check as a NUL byte.
Instead of removing bytes outside the string via a shift, force them to be
non-NUL.

* New functionality (64-bit Arm)
  * string: Optimized MTE variants of strlen, strnlen, strchr,
    strchrnul, strrchr, memchr, memrchr, strcpy, stpcpy, strcmp,
    strncmp
  * string: Changes to support BTI
  * string: New optimized memrchr, strnlen
* Performance improvements (Neoverse N1)
  * strchr/strchrnul: 21% improvement on long strings
  * strrchr: 11% improvement
  * strnlen: 130% improvement on long strings, 50% on short strings
* Benchmark and tests
  * string: New memcpy benchmark
  * string: Cleanup testsuite and improve test coverage

Ensure nul bytes before unaligned strings are correctly ignored.

Improve strcmp performance. On various micro architectures the speedup is 65%
on large unaligned strings and 21% on large (mutually) aligned strings.
On small unaligned strings the speedup is 12%.

Print results in bytes/ns. Add medium and large copy benchmark.

Set taggs for every test case so that boundaries are as narrow as
possible. There is no handling of tag faults, so the test will
crash if there is a MTE problem.

The implementations that are not compatible are excluded, including
the standard symbols that may come from an mte incompatible libc.

Clean up code and improve test coverage.

Clean up code and improve test coverage.

Clean up code and improve test coverage.

Cleanup stpcpy test and improve test coverage.

Cleanup strcpy test and improve test coverage.

Cleanup strnlen test and improve test coverage.

Cleanup strlen test and improve test coverage.

Add optimized MTE-compatible strcpy-mte and stpcpy-mte. On various micro
architectures the speedup over the non-MTE version is 53% on large strings
and 20-60% on small strings.

Improve strrchr performance by using a fast strchr loop to find the first
match. On various micro architectures the speedup is 30-80% on large strings
and 32% on small strings.

Add GNU property notes to asm files in asmdefs.h instead of adding
the END_FILE macro to each file.

The WANT_GNU_PROPERTY macro can be still used to opt-out from the
notes.