[PATCH] as-name: document that identifiers are OK for address spaces

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



A previous series allowed to used an indentifier to denotate an
address space but this wasn't documented.

Document it now in the manpage.

Signed-off-by: Luc Van Oostenryck <luc.vanoostenryck@xxxxxxxxx>
---
 sparse.1 | 7 ++++---
 1 file changed, 4 insertions(+), 3 deletions(-)

diff --git a/sparse.1 b/sparse.1
index 096c5b08c..91cd975e3 100644
--- a/sparse.1
+++ b/sparse.1
@@ -37,9 +37,10 @@ Turn all sparse warnings into errors.
 Warn about code which mixes pointers to different address spaces.
 
 Sparse allows an extended attribute
-.BI __attribute__((address_space( num )))
-on pointers, which designates a pointer target in address space \fInum\fR (a
-constant integer).  With \fB\-Waddress\-space\fR, Sparse treats pointers with
+.BI __attribute__((address_space( id )))
+on pointers, which designates a pointer target in address space \fIid\fR (an
+identifier or a constant integer).
+With \fB\-Waddress\-space\fR, Sparse treats pointers with
 identical target types but different address spaces as distinct types.  To
 override this warning, such as for functions which convert pointers between
 address spaces, use a type that includes \fB__attribute__((force))\fR.
-- 
2.20.0




[Index of Archives]     [Newbies FAQ]     [LKML]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Trinity Fuzzer Tool]

  Powered by Linux