This is the mail archive of the
glibc-bugs@sourceware.org
mailing list for the glibc project.
[Bug libc/12019] memchr overshoots on Alpha
- From: "eblake at redhat dot com" <sourceware-bugzilla at sourceware dot org>
- To: glibc-bugs at sources dot redhat dot com
- Date: 15 Sep 2010 13:41:54 -0000
- Subject: [Bug libc/12019] memchr overshoots on Alpha
- References: <20100914154213.12019.eblake@redhat.com>
- Reply-to: sourceware-bugzilla at sourceware dot org
------- Additional Comments From eblake at redhat dot com 2010-09-15 13:41 -------
Andreas: this is NOT an invalid use of memchr. Reread the Austin Group ruling
on memchr, http://www.opengroup.org/austin/docs/austin_454.txt, which I linked
to in the original post:
"A number of changes were agreed as follows
Change p1284 lines 42163-42164
In the DESCRIPTION remove "of the object" from
The memchr( ) function shall locate the first occurrence of c (converted
to an unsigned char) in the initial n bytes (each interpreted as unsigned
char) of the object pointed to by s.
In the RETURN VALUE section
The memchr( ) function shall return a pointer to the located byte,
or a null pointer if the byte does not occur in the object.
to
The memchr( ) function shall return a pointer to the located byte,
or a null pointer if the byte is not found.
Add to DESCRIPTION
Implementations shall behave as if they read the memory byte by byte
from the beginning of the bytes pointed to by s and stop at the first
occurrence of c."
Also, see http://sourceware.org/bugzilla/show_bug.cgi?id=11230, where the same
bug was fixed for IA64 for the same reason.
--
http://sourceware.org/bugzilla/show_bug.cgi?id=12019
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.