This is the mail archive of the libc-hacker@sources.redhat.com mailing list for the glibc project.
Note that libc-hacker is a closed list. You may look at the archives of this list, but subscription and posting are not open.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
On Wed, Mar 13, 2002 at 10:57:08AM +0100, Andreas Jaeger wrote: > Richard Henderson <rth@redhat.com> writes: > > > On Tue, Mar 12, 2002 at 08:38:51PM +0100, Andreas Jaeger wrote: > >> As Richard Henderson mentioned on the gcc list (see: > >> http://gcc.gnu.org/ml/gcc-patches/2002-03/msg00534.html), we need to > >> add a memory clobber even for reading memory. > > > > Err, no, I said you should describe the read from memory. > > For memcmp you have the length of the access; for the others > > you can just use an array size of 0xffffffff or something. > > A length of 0xffffffff does not work, it gives: > str.c:56: size of array `__x' is too large > I used one f less. > > But the following two examples compile. Are these ok? Don't you need __extension__ there too? Also, I think at least memcpy/memset should go for recent gcc, gcc does a better job. Jakub
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |