[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: test-memchr failure on rawhide
From: |
Bruno Haible |
Subject: |
Re: test-memchr failure on rawhide |
Date: |
Sat, 9 May 2009 00:21:03 +0200 |
User-agent: |
KMail/1.9.9 |
Andreas Schwab wrote:
> They are free to access the object in any random order they like.
The question is: How many bytes are the mem* functions free to access?
How many bytes is "the object" large?
ISO C 99 7.21.5.1 says:
"The memchr function locates the first occurrence of c (converted to an
unsigned
char) in the initial n characters (each interpreted as unsigned char) of the
object pointed to by s.
Returns
The memchr function returns a pointer to the located character, or a null
pointer
if the character does not occur in the object."
Can you give a justification why the function would be allowed to access more
than
n bytes?
Bruno
- test-memchr failure on rawhide, Jim Meyering, 2009/05/07
- Re: test-memchr failure on rawhide, Andreas Schwab, 2009/05/08
- Re: test-memchr failure on rawhide, Bruno Haible, 2009/05/08
- Re: test-memchr failure on rawhide, Andreas Schwab, 2009/05/08
- Re: test-memchr failure on rawhide, Bruno Haible, 2009/05/08
- Re: test-memchr failure on rawhide, Andreas Schwab, 2009/05/08
- Re: test-memchr failure on rawhide,
Bruno Haible <=
- Re: test-memchr failure on rawhide, James Youngman, 2009/05/08
- Re: test-memchr failure on rawhide, Bruno Haible, 2009/05/08
- Re: test-memchr failure on rawhide, Andreas Schwab, 2009/05/09
- Re: test-memchr failure on rawhide, Bruno Haible, 2009/05/09
- Re: test-memchr failure on rawhide, Andreas Schwab, 2009/05/09
- Re: test-memchr failure on rawhide, Bruno Haible, 2009/05/09
- Re: test-memchr failure on rawhide, Andreas Schwab, 2009/05/09
- Re: test-memchr failure on rawhide, Bruno Haible, 2009/05/11
- Re: test-memchr failure on rawhide, Andreas Schwab, 2009/05/11
- Re: test-memchr failure on rawhide, Ben Pfaff, 2009/05/09