<feed xmlns='http://www.w3.org/2005/Atom'>
<title>glibc.git, branch release/2.42/master</title>
<subtitle>Unnamed repository; edit this file 'description' to name the repository.
</subtitle>
<link rel='alternate' type='text/html' href='https://git.belthelziquor.com/glibc.git/'/>
<entry>
<title>ppc64le: Restore optimized strncmp for power10</title>
<updated>2025-11-21T05:31:01+00:00</updated>
<author>
<name>Sachin Monga</name>
<email>smonga@linux.ibm.com</email>
</author>
<published>2025-11-21T05:30:52+00:00</published>
<link rel='alternate' type='text/html' href='https://git.belthelziquor.com/glibc.git/commit/?id=2dbf973fe03f9b8fd5a4740ee0af0d47afdd7bbd'/>
<id>2dbf973fe03f9b8fd5a4740ee0af0d47afdd7bbd</id>
<content type='text'>
This patch addresses the actual cause of CVE-2025-5745

The vector non-volatile registers are not used anymore for
32 byte load and comparison operation

Additionally, the assembler workaround used earlier for the
instruction lxvp is replaced with actual instruction.

Signed-off-by: Sachin Monga &lt;smonga@linux.ibm.com&gt;
Co-authored-by: Paul Murphy &lt;paumurph@redhat.com&gt;
(cherry picked from commit 2ea943f7d487d6a4166658b32af7c5365889fc34)
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
This patch addresses the actual cause of CVE-2025-5745

The vector non-volatile registers are not used anymore for
32 byte load and comparison operation

Additionally, the assembler workaround used earlier for the
instruction lxvp is replaced with actual instruction.

Signed-off-by: Sachin Monga &lt;smonga@linux.ibm.com&gt;
Co-authored-by: Paul Murphy &lt;paumurph@redhat.com&gt;
(cherry picked from commit 2ea943f7d487d6a4166658b32af7c5365889fc34)
</pre>
</div>
</content>
</entry>
<entry>
<title>ppc64le: Restore optimized strcmp for power10</title>
<updated>2025-11-21T05:30:15+00:00</updated>
<author>
<name>Sachin Monga</name>
<email>smonga@linux.ibm.com</email>
</author>
<published>2025-11-21T05:30:04+00:00</published>
<link rel='alternate' type='text/html' href='https://git.belthelziquor.com/glibc.git/commit/?id=6b2957cfe8ad1e02c03a28abfc5a251c05e4005e'/>
<id>6b2957cfe8ad1e02c03a28abfc5a251c05e4005e</id>
<content type='text'>
This patch addresses the actual cause of CVE-2025-5702

The vector non-volatile registers are not used anymore for
32 byte load and comparison operation

Additionally, the assembler workaround used earlier for the
instruction lxvp is replaced with actual instruction.

Signed-off-by: Sachin Monga &lt;smonga@linux.ibm.com&gt;
Co-authored-by: Paul Murphy &lt;paumurph@redhat.com&gt;
(cherry picked from commit 9a40b1cda519cc4f532acb6d020390829df3d81b)
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
This patch addresses the actual cause of CVE-2025-5702

The vector non-volatile registers are not used anymore for
32 byte load and comparison operation

Additionally, the assembler workaround used earlier for the
instruction lxvp is replaced with actual instruction.

Signed-off-by: Sachin Monga &lt;smonga@linux.ibm.com&gt;
Co-authored-by: Paul Murphy &lt;paumurph@redhat.com&gt;
(cherry picked from commit 9a40b1cda519cc4f532acb6d020390829df3d81b)
</pre>
</div>
</content>
</entry>
<entry>
<title>AArch64: Fix and improve SVE pow(f) special cases</title>
<updated>2025-11-18T16:07:21+00:00</updated>
<author>
<name>Pierre Blanchard</name>
<email>pierre.blanchard@arm.com</email>
</author>
<published>2025-11-18T15:09:05+00:00</published>
<link rel='alternate' type='text/html' href='https://git.belthelziquor.com/glibc.git/commit/?id=828b8d23f3fa05234d35032a61a746918accf91d'/>
<id>828b8d23f3fa05234d35032a61a746918accf91d</id>
<content type='text'>
powf:

Update scalar special case function to best use new interface.

pow:

Make specialcase NOINLINE to prevent str/ldr leaking in fast path.
Remove depency in sv_call2, as new callback impl is not a
performance gain.
Replace with vectorised specialcase since structure of scalar
routine is fairly simple.

Throughput gain of about 5-10% on V1 for large values and 25% for subnormal `x`.

Reviewed-by: Wilco Dijkstra  &lt;Wilco.Dijkstra@arm.com&gt;
(cherry picked from commit bb6519de1e6fe73d79bc71588ec4e5668907f080)
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
powf:

Update scalar special case function to best use new interface.

pow:

Make specialcase NOINLINE to prevent str/ldr leaking in fast path.
Remove depency in sv_call2, as new callback impl is not a
performance gain.
Replace with vectorised specialcase since structure of scalar
routine is fairly simple.

Throughput gain of about 5-10% on V1 for large values and 25% for subnormal `x`.

Reviewed-by: Wilco Dijkstra  &lt;Wilco.Dijkstra@arm.com&gt;
(cherry picked from commit bb6519de1e6fe73d79bc71588ec4e5668907f080)
</pre>
</div>
</content>
</entry>
<entry>
<title>AArch64: fix SVE tanpi(f) [BZ #33642]</title>
<updated>2025-11-18T16:07:21+00:00</updated>
<author>
<name>Pierre Blanchard</name>
<email>pierre.blanchard@arm.com</email>
</author>
<published>2025-11-18T15:03:10+00:00</published>
<link rel='alternate' type='text/html' href='https://git.belthelziquor.com/glibc.git/commit/?id=710d7a2e8374cf09280a0db170a6c813b70b59e5'/>
<id>710d7a2e8374cf09280a0db170a6c813b70b59e5</id>
<content type='text'>
Fixed svld1rq using incorrect predicates (BZ #33642).
Next to no performance variations (tested on V1).

Reviewed-by: Wilco Dijkstra  &lt;Wilco.Dijkstra@arm.com&gt;
(cherry picked from commit e889160273a4c2b68870c9adf341955867d76a7d)
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Fixed svld1rq using incorrect predicates (BZ #33642).
Next to no performance variations (tested on V1).

Reviewed-by: Wilco Dijkstra  &lt;Wilco.Dijkstra@arm.com&gt;
(cherry picked from commit e889160273a4c2b68870c9adf341955867d76a7d)
</pre>
</div>
</content>
</entry>
<entry>
<title>AArch64: Fix instability in AdvSIMD sinh</title>
<updated>2025-11-18T16:07:21+00:00</updated>
<author>
<name>Joe Ramsay</name>
<email>Joe.Ramsay@arm.com</email>
</author>
<published>2025-11-06T18:29:33+00:00</published>
<link rel='alternate' type='text/html' href='https://git.belthelziquor.com/glibc.git/commit/?id=0c9430ed976b961343dd29b752091f3c4771cf30'/>
<id>0c9430ed976b961343dd29b752091f3c4771cf30</id>
<content type='text'>
Previously presence of special-cases in one lane could affect the
results in other lanes due to unconditional scalar fallback. The old
WANT_SIMD_EXCEPT option (which has never been enabled in libmvec) has
been removed from AOR, making it easier to spot and fix
this. No measured change in performance. This patch applies cleanly as
far back as 2.41, however there are conflicts with 2.40 where sinh was
first introduced.

Reviewed-by: Wilco Dijkstra  &lt;Wilco.Dijkstra@arm.com&gt;
(cherry picked from commit e45af510bc816e860c8e2e1d4a652b4fe15c4b34)
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Previously presence of special-cases in one lane could affect the
results in other lanes due to unconditional scalar fallback. The old
WANT_SIMD_EXCEPT option (which has never been enabled in libmvec) has
been removed from AOR, making it easier to spot and fix
this. No measured change in performance. This patch applies cleanly as
far back as 2.41, however there are conflicts with 2.40 where sinh was
first introduced.

Reviewed-by: Wilco Dijkstra  &lt;Wilco.Dijkstra@arm.com&gt;
(cherry picked from commit e45af510bc816e860c8e2e1d4a652b4fe15c4b34)
</pre>
</div>
</content>
</entry>
<entry>
<title>AArch64: Fix instability in AdvSIMD tan</title>
<updated>2025-11-18T16:07:21+00:00</updated>
<author>
<name>Joe Ramsay</name>
<email>Joe.Ramsay@arm.com</email>
</author>
<published>2025-11-06T18:26:54+00:00</published>
<link rel='alternate' type='text/html' href='https://git.belthelziquor.com/glibc.git/commit/?id=ec041b1f53bf1fd29d94ee147fac69da66437dc6'/>
<id>ec041b1f53bf1fd29d94ee147fac69da66437dc6</id>
<content type='text'>
Previously presence of special-cases in one lane could affect the
results in other lanes due to unconditional scalar fallback. The old
WANT_SIMD_EXCEPT option (which has never been enabled in libmvec) has
been removed from AOR, making it easier to spot and fix this. 4%
improvement in throughput with GCC 14 on Neoverse V1. This bug is
present as far back as 2.39 (where tan was first introduced).

Reviewed-by: Wilco Dijkstra  &lt;Wilco.Dijkstra@arm.com&gt;
(cherry picked from commit 6c22823da57aa5218f717f569c04c9573c0448c5)
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Previously presence of special-cases in one lane could affect the
results in other lanes due to unconditional scalar fallback. The old
WANT_SIMD_EXCEPT option (which has never been enabled in libmvec) has
been removed from AOR, making it easier to spot and fix this. 4%
improvement in throughput with GCC 14 on Neoverse V1. This bug is
present as far back as 2.39 (where tan was first introduced).

Reviewed-by: Wilco Dijkstra  &lt;Wilco.Dijkstra@arm.com&gt;
(cherry picked from commit 6c22823da57aa5218f717f569c04c9573c0448c5)
</pre>
</div>
</content>
</entry>
<entry>
<title>AArch64: Optimise SVE scalar callbacks</title>
<updated>2025-11-18T16:07:21+00:00</updated>
<author>
<name>Joe Ramsay</name>
<email>Joe.Ramsay@arm.com</email>
</author>
<published>2025-11-06T15:36:03+00:00</published>
<link rel='alternate' type='text/html' href='https://git.belthelziquor.com/glibc.git/commit/?id=97297120ce04f0edd16ed0357a11ef8731c5bd1e'/>
<id>97297120ce04f0edd16ed0357a11ef8731c5bd1e</id>
<content type='text'>
Instead of using SVE instructions to marshall special results into the
correct lane, just write the entire vector (and the predicate) to
memory, then use cheaper scalar operations.

Geomean speedup of 16% in special intervals on Neoverse with GCC 14.

Reviewed-by: Wilco Dijkstra  &lt;Wilco.Dijkstra@arm.com&gt;
(cherry picked from commit 5b82fb18827e962af9f080fdf3c1a69802783f67)
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Instead of using SVE instructions to marshall special results into the
correct lane, just write the entire vector (and the predicate) to
memory, then use cheaper scalar operations.

Geomean speedup of 16% in special intervals on Neoverse with GCC 14.

Reviewed-by: Wilco Dijkstra  &lt;Wilco.Dijkstra@arm.com&gt;
(cherry picked from commit 5b82fb18827e962af9f080fdf3c1a69802783f67)
</pre>
</div>
</content>
</entry>
<entry>
<title>aarch64: fix includes in SME tests</title>
<updated>2025-11-13T13:06:49+00:00</updated>
<author>
<name>Yury Khrustalev</name>
<email>yury.khrustalev@arm.com</email>
</author>
<published>2025-11-11T11:40:25+00:00</published>
<link rel='alternate' type='text/html' href='https://git.belthelziquor.com/glibc.git/commit/?id=17c3eab387c3ceb6972e57888a89b1480793f81a'/>
<id>17c3eab387c3ceb6972e57888a89b1480793f81a</id>
<content type='text'>
Use the correct include for the SIGCHLD macro: signal.h

Reviewed-by: Wilco Dijkstra  &lt;Wilco.Dijkstra@arm.com&gt;
(cherry picked from commit a9c426bcca59a9e228c4fbe75e75154217ec4ada)
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Use the correct include for the SIGCHLD macro: signal.h

Reviewed-by: Wilco Dijkstra  &lt;Wilco.Dijkstra@arm.com&gt;
(cherry picked from commit a9c426bcca59a9e228c4fbe75e75154217ec4ada)
</pre>
</div>
</content>
</entry>
<entry>
<title>aarch64: fix cfi directives around __libc_arm_za_disable</title>
<updated>2025-11-10T10:02:58+00:00</updated>
<author>
<name>Yury Khrustalev</name>
<email>yury.khrustalev@arm.com</email>
</author>
<published>2025-10-28T11:01:50+00:00</published>
<link rel='alternate' type='text/html' href='https://git.belthelziquor.com/glibc.git/commit/?id=de1fe81f471496366580ad728b8986a3424b2fd7'/>
<id>de1fe81f471496366580ad728b8986a3424b2fd7</id>
<content type='text'>
Incorrect CFI directive corrupted call stack information
and prevented debuggers from correctly displaying call
stack information.

Reviewed-by: Adhemerval Zanella  &lt;adhemerval.zanella@linaro.org&gt;
(cherry picked from commit 2f77aec043f61e8533487850b11941a640ae2dea)
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Incorrect CFI directive corrupted call stack information
and prevented debuggers from correctly displaying call
stack information.

Reviewed-by: Adhemerval Zanella  &lt;adhemerval.zanella@linaro.org&gt;
(cherry picked from commit 2f77aec043f61e8533487850b11941a640ae2dea)
</pre>
</div>
</content>
</entry>
<entry>
<title>x86: fix wmemset ifunc stray '!' (bug 33542)</title>
<updated>2025-11-04T12:22:09+00:00</updated>
<author>
<name>Jiamei Xie</name>
<email>xiejiamei@hygon.cn</email>
</author>
<published>2025-10-14T12:14:11+00:00</published>
<link rel='alternate' type='text/html' href='https://git.belthelziquor.com/glibc.git/commit/?id=bf499c2a4964bddc25a006ec1402f8996d78c6ff'/>
<id>bf499c2a4964bddc25a006ec1402f8996d78c6ff</id>
<content type='text'>
The ifunc selector for wmemset had a stray '!' in the
X86_ISA_CPU_FEATURES_ARCH_P(...) check:

  if (X86_ISA_CPU_FEATURE_USABLE_P (cpu_features, AVX2)
      &amp;&amp; X86_ISA_CPU_FEATURES_ARCH_P (cpu_features,
                                      AVX_Fast_Unaligned_Load, !))

This effectively negated the predicate and caused the AVX2/AVX512
paths to be skipped, making the dispatcher fall back to the SSE2
implementation even on CPUs where AVX2/AVX512 are available. The
regression leads to noticeable throughput loss for wmemset.

Remove the stray '!' so the AVX_Fast_Unaligned_Load capability is
tested as intended and the correct AVX2/EVEX variants are selected.

Impact:
- On AVX2/AVX512-capable x86_64, wmemset no longer incorrectly
  falls back to SSE2; perf now shows __wmemset_evex/avx2 variants.

Testing:
- benchtests/bench-wmemset shows improved bandwidth across sizes.
- perf confirm the selected symbol is no longer SSE2.

Signed-off-by: xiejiamei &lt;xiejiamei@hygon.com&gt;
Signed-off-by: Li jing &lt;lijing@hygon.cn&gt;
Reviewed-by: Adhemerval Zanella  &lt;adhemerval.zanella@linaro.org&gt;
(cherry picked from commit 4d86b6cdd8132e0410347e07262239750f86dfb4)
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
The ifunc selector for wmemset had a stray '!' in the
X86_ISA_CPU_FEATURES_ARCH_P(...) check:

  if (X86_ISA_CPU_FEATURE_USABLE_P (cpu_features, AVX2)
      &amp;&amp; X86_ISA_CPU_FEATURES_ARCH_P (cpu_features,
                                      AVX_Fast_Unaligned_Load, !))

This effectively negated the predicate and caused the AVX2/AVX512
paths to be skipped, making the dispatcher fall back to the SSE2
implementation even on CPUs where AVX2/AVX512 are available. The
regression leads to noticeable throughput loss for wmemset.

Remove the stray '!' so the AVX_Fast_Unaligned_Load capability is
tested as intended and the correct AVX2/EVEX variants are selected.

Impact:
- On AVX2/AVX512-capable x86_64, wmemset no longer incorrectly
  falls back to SSE2; perf now shows __wmemset_evex/avx2 variants.

Testing:
- benchtests/bench-wmemset shows improved bandwidth across sizes.
- perf confirm the selected symbol is no longer SSE2.

Signed-off-by: xiejiamei &lt;xiejiamei@hygon.com&gt;
Signed-off-by: Li jing &lt;lijing@hygon.cn&gt;
Reviewed-by: Adhemerval Zanella  &lt;adhemerval.zanella@linaro.org&gt;
(cherry picked from commit 4d86b6cdd8132e0410347e07262239750f86dfb4)
</pre>
</div>
</content>
</entry>
</feed>
