[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: test-memchr failure on rawhide
From: |
Andreas Schwab |
Subject: |
Re: test-memchr failure on rawhide |
Date: |
Fri, 08 May 2009 12:55:51 +0200 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/23.0.93 (gnu/linux) |
Bruno Haible <address@hidden> writes:
> Andreas Schwab wrote:
>> This is not a bug. NULL is not a valid object pointer.
>
> Do you mean to say that none of the functions
> memchr
> memcmp
> memcpy
> memmove
> memset
> wmemchr
> wmemcmp
> wmemcpy
> wmemmove
> wmemset
> may be called with arguments ptr = NULL and n = 0 ?
As described in 7.21.1#2, the pointer argument must always be a valid
pointer to an object.
> This would certainly be a departure from historical practice.
Implementations are free to define undefined behaviour any way they
like. The C standard imposes no restrictions on that behaviour.
Andreas.
--
Andreas Schwab, address@hidden
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
- 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 <=
- 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, 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