Home
last modified time | relevance | path

Searched refs:__bitwise (Results 1 – 8 of 8) sorted by last modified time

/illumos-gate/usr/src/tools/smatch/src/validation/
H A Dtypeof-mods.c2 #define __bitwise __attribute__((bitwise)) macro
76 typedef int __bitwise type_t; in test_bitwise()
H A Dtype-compare.c4 #define __bitwise __attribute__((bitwise)) macro
52 if ([int] == [int __bitwise]) return 1; in test()
60 if ([int *] == [int __bitwise *]) return 1; in test()
H A Dptr-inherit.c3 #define __bitwise __attribute__((bitwise)) macro
29 int __bitwise o; in test_bitwise()
H A Denum-bitwise.c1 #define __bitwise __attribute__((bitwise)) macro
4 typedef long long __bitwise bits;
H A Denum-bitwise-bad.c1 #define __bitwise __attribute__((bitwise)) macro
4 typedef int __bitwise apple_t;
5 typedef int __bitwise orange_t;
H A Denum-bitwise-mixed.c1 #define __bitwise __attribute__((bitwise)) macro
4 typedef long long __bitwise bits;
H A Dbitwise-cast-ptr.c1 #define __bitwise __attribute__((bitwise)) macro
5 typedef unsigned int __bitwise __be32;
/illumos-gate/usr/src/tools/smatch/src/Documentation/
H A Dnocast-vs-bitwise.md1 # __nocast vs __bitwise
13 `__bitwise` ends up being a *stronger integer separation*. That one
27 - `__bitwise` is for *unique types* that cannot be mixed with other
31 types would be `__bitwise`: you can only operate on them by doing
34 Generally, you want `__bitwise` if you are looking for type safety.
39 * Linus' e-mail about `__nocast` vs `__bitwise`: