annotate lib/rawmemchr.c @ 273:88bbffa404ea 2.5 2.5

Updated version for release
author lost
date Sun, 16 Aug 2009 17:18:11 +0000
parents d5392bb5da3c
children
Ignore whitespace changes - Everywhere: Within whitespace: At end of lines:
rev   line source
272
d5392bb5da3c Added generated files
lost
parents:
diff changeset
1 /* Searching in a string.
d5392bb5da3c Added generated files
lost
parents:
diff changeset
2 Copyright (C) 2008 Free Software Foundation, Inc.
d5392bb5da3c Added generated files
lost
parents:
diff changeset
3
d5392bb5da3c Added generated files
lost
parents:
diff changeset
4 This program is free software: you can redistribute it and/or modify
d5392bb5da3c Added generated files
lost
parents:
diff changeset
5 it under the terms of the GNU General Public License as published by
d5392bb5da3c Added generated files
lost
parents:
diff changeset
6 the Free Software Foundation; either version 3 of the License, or
d5392bb5da3c Added generated files
lost
parents:
diff changeset
7 (at your option) any later version.
d5392bb5da3c Added generated files
lost
parents:
diff changeset
8
d5392bb5da3c Added generated files
lost
parents:
diff changeset
9 This program is distributed in the hope that it will be useful,
d5392bb5da3c Added generated files
lost
parents:
diff changeset
10 but WITHOUT ANY WARRANTY; without even the implied warranty of
d5392bb5da3c Added generated files
lost
parents:
diff changeset
11 MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
d5392bb5da3c Added generated files
lost
parents:
diff changeset
12 GNU General Public License for more details.
d5392bb5da3c Added generated files
lost
parents:
diff changeset
13
d5392bb5da3c Added generated files
lost
parents:
diff changeset
14 You should have received a copy of the GNU General Public License
d5392bb5da3c Added generated files
lost
parents:
diff changeset
15 along with this program. If not, see <http://www.gnu.org/licenses/>. */
d5392bb5da3c Added generated files
lost
parents:
diff changeset
16
d5392bb5da3c Added generated files
lost
parents:
diff changeset
17 #include <config.h>
d5392bb5da3c Added generated files
lost
parents:
diff changeset
18
d5392bb5da3c Added generated files
lost
parents:
diff changeset
19 /* Specification. */
d5392bb5da3c Added generated files
lost
parents:
diff changeset
20 #include <string.h>
d5392bb5da3c Added generated files
lost
parents:
diff changeset
21
d5392bb5da3c Added generated files
lost
parents:
diff changeset
22 /* Find the first occurrence of C in S. */
d5392bb5da3c Added generated files
lost
parents:
diff changeset
23 void *
d5392bb5da3c Added generated files
lost
parents:
diff changeset
24 rawmemchr (const void *s, int c_in)
d5392bb5da3c Added generated files
lost
parents:
diff changeset
25 {
d5392bb5da3c Added generated files
lost
parents:
diff changeset
26 /* On 32-bit hardware, choosing longword to be a 32-bit unsigned
d5392bb5da3c Added generated files
lost
parents:
diff changeset
27 long instead of a 64-bit uintmax_t tends to give better
d5392bb5da3c Added generated files
lost
parents:
diff changeset
28 performance. On 64-bit hardware, unsigned long is generally 64
d5392bb5da3c Added generated files
lost
parents:
diff changeset
29 bits already. Change this typedef to experiment with
d5392bb5da3c Added generated files
lost
parents:
diff changeset
30 performance. */
d5392bb5da3c Added generated files
lost
parents:
diff changeset
31 typedef unsigned long int longword;
d5392bb5da3c Added generated files
lost
parents:
diff changeset
32
d5392bb5da3c Added generated files
lost
parents:
diff changeset
33 const unsigned char *char_ptr;
d5392bb5da3c Added generated files
lost
parents:
diff changeset
34 const longword *longword_ptr;
d5392bb5da3c Added generated files
lost
parents:
diff changeset
35 longword repeated_one;
d5392bb5da3c Added generated files
lost
parents:
diff changeset
36 longword repeated_c;
d5392bb5da3c Added generated files
lost
parents:
diff changeset
37 unsigned char c;
d5392bb5da3c Added generated files
lost
parents:
diff changeset
38
d5392bb5da3c Added generated files
lost
parents:
diff changeset
39 c = (unsigned char) c_in;
d5392bb5da3c Added generated files
lost
parents:
diff changeset
40
d5392bb5da3c Added generated files
lost
parents:
diff changeset
41 /* Handle the first few bytes by reading one byte at a time.
d5392bb5da3c Added generated files
lost
parents:
diff changeset
42 Do this until CHAR_PTR is aligned on a longword boundary. */
d5392bb5da3c Added generated files
lost
parents:
diff changeset
43 for (char_ptr = (const unsigned char *) s;
d5392bb5da3c Added generated files
lost
parents:
diff changeset
44 (size_t) char_ptr % sizeof (longword) != 0;
d5392bb5da3c Added generated files
lost
parents:
diff changeset
45 ++char_ptr)
d5392bb5da3c Added generated files
lost
parents:
diff changeset
46 if (*char_ptr == c)
d5392bb5da3c Added generated files
lost
parents:
diff changeset
47 return (void *) char_ptr;
d5392bb5da3c Added generated files
lost
parents:
diff changeset
48
d5392bb5da3c Added generated files
lost
parents:
diff changeset
49 longword_ptr = (const longword *) char_ptr;
d5392bb5da3c Added generated files
lost
parents:
diff changeset
50
d5392bb5da3c Added generated files
lost
parents:
diff changeset
51 /* All these elucidatory comments refer to 4-byte longwords,
d5392bb5da3c Added generated files
lost
parents:
diff changeset
52 but the theory applies equally well to any size longwords. */
d5392bb5da3c Added generated files
lost
parents:
diff changeset
53
d5392bb5da3c Added generated files
lost
parents:
diff changeset
54 /* Compute auxiliary longword values:
d5392bb5da3c Added generated files
lost
parents:
diff changeset
55 repeated_one is a value which has a 1 in every byte.
d5392bb5da3c Added generated files
lost
parents:
diff changeset
56 repeated_c has c in every byte. */
d5392bb5da3c Added generated files
lost
parents:
diff changeset
57 repeated_one = 0x01010101;
d5392bb5da3c Added generated files
lost
parents:
diff changeset
58 repeated_c = c | (c << 8);
d5392bb5da3c Added generated files
lost
parents:
diff changeset
59 repeated_c |= repeated_c << 16;
d5392bb5da3c Added generated files
lost
parents:
diff changeset
60 if (0xffffffffU < (longword) -1)
d5392bb5da3c Added generated files
lost
parents:
diff changeset
61 {
d5392bb5da3c Added generated files
lost
parents:
diff changeset
62 repeated_one |= repeated_one << 31 << 1;
d5392bb5da3c Added generated files
lost
parents:
diff changeset
63 repeated_c |= repeated_c << 31 << 1;
d5392bb5da3c Added generated files
lost
parents:
diff changeset
64 if (8 < sizeof (longword))
d5392bb5da3c Added generated files
lost
parents:
diff changeset
65 {
d5392bb5da3c Added generated files
lost
parents:
diff changeset
66 size_t i;
d5392bb5da3c Added generated files
lost
parents:
diff changeset
67
d5392bb5da3c Added generated files
lost
parents:
diff changeset
68 for (i = 64; i < sizeof (longword) * 8; i *= 2)
d5392bb5da3c Added generated files
lost
parents:
diff changeset
69 {
d5392bb5da3c Added generated files
lost
parents:
diff changeset
70 repeated_one |= repeated_one << i;
d5392bb5da3c Added generated files
lost
parents:
diff changeset
71 repeated_c |= repeated_c << i;
d5392bb5da3c Added generated files
lost
parents:
diff changeset
72 }
d5392bb5da3c Added generated files
lost
parents:
diff changeset
73 }
d5392bb5da3c Added generated files
lost
parents:
diff changeset
74 }
d5392bb5da3c Added generated files
lost
parents:
diff changeset
75
d5392bb5da3c Added generated files
lost
parents:
diff changeset
76 /* Instead of the traditional loop which tests each byte, we will
d5392bb5da3c Added generated files
lost
parents:
diff changeset
77 test a longword at a time. The tricky part is testing if *any of
d5392bb5da3c Added generated files
lost
parents:
diff changeset
78 the four* bytes in the longword in question are equal to NUL or
d5392bb5da3c Added generated files
lost
parents:
diff changeset
79 c. We first use an xor with repeated_c. This reduces the task
d5392bb5da3c Added generated files
lost
parents:
diff changeset
80 to testing whether *any of the four* bytes in longword1 is zero.
d5392bb5da3c Added generated files
lost
parents:
diff changeset
81
d5392bb5da3c Added generated files
lost
parents:
diff changeset
82 We compute tmp =
d5392bb5da3c Added generated files
lost
parents:
diff changeset
83 ((longword1 - repeated_one) & ~longword1) & (repeated_one << 7).
d5392bb5da3c Added generated files
lost
parents:
diff changeset
84 That is, we perform the following operations:
d5392bb5da3c Added generated files
lost
parents:
diff changeset
85 1. Subtract repeated_one.
d5392bb5da3c Added generated files
lost
parents:
diff changeset
86 2. & ~longword1.
d5392bb5da3c Added generated files
lost
parents:
diff changeset
87 3. & a mask consisting of 0x80 in every byte.
d5392bb5da3c Added generated files
lost
parents:
diff changeset
88 Consider what happens in each byte:
d5392bb5da3c Added generated files
lost
parents:
diff changeset
89 - If a byte of longword1 is zero, step 1 and 2 transform it into 0xff,
d5392bb5da3c Added generated files
lost
parents:
diff changeset
90 and step 3 transforms it into 0x80. A carry can also be propagated
d5392bb5da3c Added generated files
lost
parents:
diff changeset
91 to more significant bytes.
d5392bb5da3c Added generated files
lost
parents:
diff changeset
92 - If a byte of longword1 is nonzero, let its lowest 1 bit be at
d5392bb5da3c Added generated files
lost
parents:
diff changeset
93 position k (0 <= k <= 7); so the lowest k bits are 0. After step 1,
d5392bb5da3c Added generated files
lost
parents:
diff changeset
94 the byte ends in a single bit of value 0 and k bits of value 1.
d5392bb5da3c Added generated files
lost
parents:
diff changeset
95 After step 2, the result is just k bits of value 1: 2^k - 1. After
d5392bb5da3c Added generated files
lost
parents:
diff changeset
96 step 3, the result is 0. And no carry is produced.
d5392bb5da3c Added generated files
lost
parents:
diff changeset
97 So, if longword1 has only non-zero bytes, tmp is zero.
d5392bb5da3c Added generated files
lost
parents:
diff changeset
98 Whereas if longword1 has a zero byte, call j the position of the least
d5392bb5da3c Added generated files
lost
parents:
diff changeset
99 significant zero byte. Then the result has a zero at positions 0, ...,
d5392bb5da3c Added generated files
lost
parents:
diff changeset
100 j-1 and a 0x80 at position j. We cannot predict the result at the more
d5392bb5da3c Added generated files
lost
parents:
diff changeset
101 significant bytes (positions j+1..3), but it does not matter since we
d5392bb5da3c Added generated files
lost
parents:
diff changeset
102 already have a non-zero bit at position 8*j+7.
d5392bb5da3c Added generated files
lost
parents:
diff changeset
103
d5392bb5da3c Added generated files
lost
parents:
diff changeset
104 The test whether any byte in longword1 is zero is equivalent
d5392bb5da3c Added generated files
lost
parents:
diff changeset
105 to testing whether tmp is nonzero.
d5392bb5da3c Added generated files
lost
parents:
diff changeset
106
d5392bb5da3c Added generated files
lost
parents:
diff changeset
107 This test can read beyond the end of a string, depending on where
d5392bb5da3c Added generated files
lost
parents:
diff changeset
108 C_IN is encountered. However, this is considered safe since the
d5392bb5da3c Added generated files
lost
parents:
diff changeset
109 initialization phase ensured that the read will be aligned,
d5392bb5da3c Added generated files
lost
parents:
diff changeset
110 therefore, the read will not cross page boundaries and will not
d5392bb5da3c Added generated files
lost
parents:
diff changeset
111 cause a fault. */
d5392bb5da3c Added generated files
lost
parents:
diff changeset
112
d5392bb5da3c Added generated files
lost
parents:
diff changeset
113 while (1)
d5392bb5da3c Added generated files
lost
parents:
diff changeset
114 {
d5392bb5da3c Added generated files
lost
parents:
diff changeset
115 longword longword1 = *longword_ptr ^ repeated_c;
d5392bb5da3c Added generated files
lost
parents:
diff changeset
116
d5392bb5da3c Added generated files
lost
parents:
diff changeset
117 if ((((longword1 - repeated_one) & ~longword1)
d5392bb5da3c Added generated files
lost
parents:
diff changeset
118 & (repeated_one << 7)) != 0)
d5392bb5da3c Added generated files
lost
parents:
diff changeset
119 break;
d5392bb5da3c Added generated files
lost
parents:
diff changeset
120 longword_ptr++;
d5392bb5da3c Added generated files
lost
parents:
diff changeset
121 }
d5392bb5da3c Added generated files
lost
parents:
diff changeset
122
d5392bb5da3c Added generated files
lost
parents:
diff changeset
123 char_ptr = (const unsigned char *) longword_ptr;
d5392bb5da3c Added generated files
lost
parents:
diff changeset
124
d5392bb5da3c Added generated files
lost
parents:
diff changeset
125 /* At this point, we know that one of the sizeof (longword) bytes
d5392bb5da3c Added generated files
lost
parents:
diff changeset
126 starting at char_ptr is == c. On little-endian machines, we
d5392bb5da3c Added generated files
lost
parents:
diff changeset
127 could determine the first such byte without any further memory
d5392bb5da3c Added generated files
lost
parents:
diff changeset
128 accesses, just by looking at the tmp result from the last loop
d5392bb5da3c Added generated files
lost
parents:
diff changeset
129 iteration. But this does not work on big-endian machines.
d5392bb5da3c Added generated files
lost
parents:
diff changeset
130 Choose code that works in both cases. */
d5392bb5da3c Added generated files
lost
parents:
diff changeset
131
d5392bb5da3c Added generated files
lost
parents:
diff changeset
132 char_ptr = (unsigned char *) longword_ptr;
d5392bb5da3c Added generated files
lost
parents:
diff changeset
133 while (*char_ptr != c)
d5392bb5da3c Added generated files
lost
parents:
diff changeset
134 char_ptr++;
d5392bb5da3c Added generated files
lost
parents:
diff changeset
135 return (void *) char_ptr;
d5392bb5da3c Added generated files
lost
parents:
diff changeset
136 }