<feed xmlns='http://www.w3.org/2005/Atom'>
<title>glibc/string/Makefile, branch vdso</title>
<subtitle>Fork of glibc for development</subtitle>
<id>https://git.zx2c4.com/glibc/atom/string/Makefile?h=vdso</id>
<link rel='self' href='https://git.zx2c4.com/glibc/atom/string/Makefile?h=vdso'/>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/glibc/'/>
<updated>2024-08-01T07:08:32Z</updated>
<entry>
<title>Enhanced test coverage for strncmp, wcsncmp</title>
<updated>2024-08-01T07:08:32Z</updated>
<author>
<name>Florian Weimer</name>
<email>fweimer@redhat.com</email>
</author>
<published>2024-06-27T14:26:56Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/glibc/commit/?id=54252394c25ddf0062e288d4a6ab7a885f8ae009'/>
<id>urn:sha1:54252394c25ddf0062e288d4a6ab7a885f8ae009</id>
<content type='text'>
Add string/test-strncmp-nonarray and
wcsmbs/test-wcsncmp-nonarray.

This is the test that uncovered bug 31934.  Test run time
is more than one minute on a fairly current system, so turn
these into xtests that do not run automatically.

Reviewed-by: Noah Goldstein &lt;goldstein.w.n@gmail.com&gt;
</content>
</entry>
<entry>
<title>Enhance test coverage for strnlen, wcsnlen</title>
<updated>2024-08-01T07:07:34Z</updated>
<author>
<name>Florian Weimer</name>
<email>fweimer@redhat.com</email>
</author>
<published>2024-06-26T09:27:54Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/glibc/commit/?id=783d4c0b81889c39a9ddf13b60d0fde4040fb1c0'/>
<id>urn:sha1:783d4c0b81889c39a9ddf13b60d0fde4040fb1c0</id>
<content type='text'>
This commit adds string/test-strnlen-nonarray and
wcsmbs/test-wcsnlen-nonarray.

Reviewed-by: Noah Goldstein &lt;goldstein.w.n@gmail.com&gt;
</content>
</entry>
<entry>
<title>string: Disable stack protector for memset in early static initialization</title>
<updated>2024-01-23T13:22:59Z</updated>
<author>
<name>Adhemerval Zanella</name>
<email>adhemerval.zanella@linaro.org</email>
</author>
<published>2024-01-22T13:42:19Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/glibc/commit/?id=77c6a2717de1b6a78e79538b2074579ed77839ed'/>
<id>urn:sha1:77c6a2717de1b6a78e79538b2074579ed77839ed</id>
<content type='text'>
For ports that use the default memset, the compiler might generate early
calls before the stack protector is initialized (for instance, riscv
with -fstack-protector-all on _dl_aux_init).

Checked on riscv64-linux-gnu-rv64imafdc-lp64d.

Reviewed-by: Florian Weimer &lt;fweimer@redhat.com&gt;
</content>
</entry>
<entry>
<title>Update copyright dates with scripts/update-copyrights</title>
<updated>2024-01-01T18:53:40Z</updated>
<author>
<name>Paul Eggert</name>
<email>eggert@cs.ucla.edu</email>
</author>
<published>2024-01-01T18:12:26Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/glibc/commit/?id=dff8da6b3e89b986bb7f6b1ec18cf65d5972e307'/>
<id>urn:sha1:dff8da6b3e89b986bb7f6b1ec18cf65d5972e307</id>
<content type='text'>
</content>
</entry>
<entry>
<title>string: Add internal memswap implementation</title>
<updated>2023-10-31T17:17:33Z</updated>
<author>
<name>Adhemerval Zanella</name>
<email>adhemerval.zanella@linaro.org</email>
</author>
<published>2023-10-03T12:22:45Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/glibc/commit/?id=fccf38c51746e0817c2409bb361398f9465e0760'/>
<id>urn:sha1:fccf38c51746e0817c2409bb361398f9465e0760</id>
<content type='text'>
The prototype is:

  void __memswap (void *restrict p1, void *restrict p2, size_t n)

The function swaps the content of two memory blocks P1 and P2 of
len N.  Memory overlap is NOT handled.

It will be used on qsort optimization.

Checked on x86_64-linux-gnu and aarch64-linux-gnu.
Reviewed-by: Noah Goldstein &lt;goldstein.w.n@gmail.com&gt;
</content>
</entry>
<entry>
<title>Add strlcat/wcslcat testcase.</title>
<updated>2023-10-17T22:19:01Z</updated>
<author>
<name>Sunil K Pandey</name>
<email>skpgkp2@gmail.com</email>
</author>
<published>2023-07-27T23:20:49Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/glibc/commit/?id=b316c9a76903fec1596642b3020b3f939c05b8db'/>
<id>urn:sha1:b316c9a76903fec1596642b3020b3f939c05b8db</id>
<content type='text'>
This patch implements comprehensive tests for strlcat/wcslcat
functions.  Tests are mostly derived from strncat test suites
and modified to incorporate strlcat/wcslcat specifications.

Reviewed-by: DJ Delorie &lt;dj@redhat.com&gt;
</content>
</entry>
<entry>
<title>Add strlcpy/wcslcpy testcase</title>
<updated>2023-10-17T22:18:55Z</updated>
<author>
<name>Sunil K Pandey</name>
<email>skpgkp2@gmail.com</email>
</author>
<published>2023-07-27T23:20:37Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/glibc/commit/?id=23871292fb25d1bf4d17e73490614ea2a3001d78'/>
<id>urn:sha1:23871292fb25d1bf4d17e73490614ea2a3001d78</id>
<content type='text'>
This patch implements comprehensive tests for strlcpy/wcslcpy
functions.  Tests are mostly derived from strncpy test suites
and modified to incorporate strlcpy/wcslcpy specifications.

Reviewed-by: DJ Delorie &lt;dj@redhat.com&gt;
</content>
</entry>
<entry>
<title>Exclude routines from fortification</title>
<updated>2023-07-05T14:59:48Z</updated>
<author>
<name>Frédéric Bérat</name>
<email>fberat@redhat.com</email>
</author>
<published>2023-03-17T09:17:28Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/glibc/commit/?id=20c894d21eb64153abf7c7f96e6a151897cf1488'/>
<id>urn:sha1:20c894d21eb64153abf7c7f96e6a151897cf1488</id>
<content type='text'>
Since the _FORTIFY_SOURCE feature uses some routines of Glibc, they need to
be excluded from the fortification.

On top of that:
 - some tests explicitly verify that some level of fortification works
   appropriately, we therefore shouldn't modify the level set for them.
 - some objects need to be build with optimization disabled, which
   prevents _FORTIFY_SOURCE to be used for them.

Assembler files that implement architecture specific versions of the
fortified routines were not excluded from _FORTIFY_SOURCE as there is no
C header included that would impact their behavior.

Reviewed-by: Siddhesh Poyarekar &lt;siddhesh@sourceware.org&gt;
</content>
</entry>
<entry>
<title>string: strerror must not return NULL (bug 30555)</title>
<updated>2023-06-15T17:54:09Z</updated>
<author>
<name>Florian Weimer</name>
<email>fweimer@redhat.com</email>
</author>
<published>2023-06-15T10:08:22Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/glibc/commit/?id=1d44530a5be2442e064baa48139adc9fdfb1fc6b'/>
<id>urn:sha1:1d44530a5be2442e064baa48139adc9fdfb1fc6b</id>
<content type='text'>
For strerror, this fixes commit 28aff047818eb1726394296d27b ("string:
Implement strerror in terms of strerror_l").  This commit avoids
returning NULL for strerror_l as well, although POSIX allows this
behavior for strerror_l.

Reviewed-by: Arjun Shankar &lt;arjun@redhat.com&gt;
</content>
</entry>
<entry>
<title>Implement strlcpy and strlcat [BZ #178]</title>
<updated>2023-06-14T16:10:08Z</updated>
<author>
<name>Florian Weimer</name>
<email>fweimer@redhat.com</email>
</author>
<published>2023-06-14T16:10:08Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/glibc/commit/?id=454a20c8756c9c1d55419153255fc7692b3d2199'/>
<id>urn:sha1:454a20c8756c9c1d55419153255fc7692b3d2199</id>
<content type='text'>
These functions are about to be added to POSIX, under Austin Group
issue 986.

The fortified strlcat implementation does not raise SIGABRT if the
destination buffer does not contain a null terminator, it just
inherits the non-failing regular strlcat behavior.

Reviewed-by: Siddhesh Poyarekar &lt;siddhesh@sourceware.org&gt;
</content>
</entry>
</feed>
