diff options
author | Luc Van Oostenryck <luc.vanoostenryck@gmail.com> | 2018-12-22 01:15:23 +0100 |
---|---|---|
committer | Luc Van Oostenryck <luc.vanoostenryck@gmail.com> | 2018-12-22 01:17:28 +0100 |
commit | 2369d107e245400ff07218d29b14593b559dca20 (patch) | |
tree | b1ea87db8f9bd41a7c1a02fd8a708485734608d9 | |
parent | 951a3d03869a4ae639abeee5547ae32d845a2d3e (diff) | |
download | sparse-2369d107e245400ff07218d29b14593b559dca20.tar.gz |
as-name: document that identifiers are OK for address spaces
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@gmail.com>
-rw-r--r-- | sparse.1 | 7 |
1 files changed, 4 insertions, 3 deletions
@@ -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. |