Eric Blake wrote:
According to Bruno Haible on 5/26/2009 4:05 PM:
Eric Blake wrote:
http://www.alphalinux.org/archives/axp-list/March2001/0337.shtml
It looks like the bug is alpha-specific in memchr
I don't think it is a bug. memchr could also be implemented by doing
a backwards search and still be conforming to ISO C99 and POSIX:
The Austin Group disagrees with you. Here is the results from the meeting
yesterday
(https://www.opengroup.org/sophocles/show_mail.tpl?CALLER=index.tpl&source=L&listname=austin-group-l&id=12144):
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.
Doesn't that preclude *any* sort of optimization? Or is it always safe
to read up to the end of a word boundary?
--
Matthew
Please do not quote my e-mail address unobfuscated in message bodies.
--
<insert witty signature here>
