This is the mail archive of the
libc-alpha@sources.redhat.com
mailing list for the glibc project.
sysdeps/i386/i486/bits/string.h: describing memory access question
- From: Denis Zaitsev <zzz at cd-club dot ru>
- To: aj at suse dot de
- Cc: libc-alpha at sources dot redhat dot com
- Date: Sun, 12 Jan 2003 02:35:52 +0500
- Subject: sysdeps/i386/i486/bits/string.h: describing memory access question
So, just everyhere we have (for now) something like
"m" ( *(struct { char __x[0xfffffff]; } *)__str)
in the input parameters list. The question is: why 0xfffffff is used?
Would 0x7fffffff be better? As it describes all the usable memory,
not just 1/8 part of it.
And would it be better to use some macros for this, like:
"m" (*(ALL_MEM*)__str)
along with, say:
"m" (*(PART_MEM(__len)*)__mem)
for __mem[__len] parameters. It seems to be more readable and more
convinient and more etc. I would like to implement this, if the idea
in general is sane.