Searched refs:__nocast (Results 1 – 5 of 5) sorted by relevance
1 # __nocast vs __bitwise3 `__nocast` warns about explicit or implicit casting to different types.5 types, so a `__nocast int` type may be returned as a regular `int`6 type and then the `__nocast` is lost.8 So `__nocast` on integer types is usually not that powerful. It just10 also doesn't warn about the mixing: you can add integers to `__nocast`19 - `__nocast` on its own tends to be more useful for *big* integers25 means that the `__nocast` really gets lost fairly easily.35 `__nocast` really is pretty weak.39 * Linus' e-mail about `__nocast` vs `__bitwise`:
1 #define __nocast __attribute__((nocast)) macro2 typedef unsigned long __nocast ulong_nc_t;83 unsigned long long __nocast *bad_size = t; in assign_ptr()84 short __nocast *bad_i = t; in assign_ptr()85 long __nocast *bad_l = t; in assign_ptr()
3 #define __nocast __attribute__((nocast)) macro51 if ([int] == [int __nocast]) return 1; in test()59 if ([int *] == [int __nocast *]) return 1; in test()
4 #define __nocast __attribute__((nocast)) macro41 int __nocast o; in test_nocast()42 int __nocast *p = &o; /* check-should-pass */ in test_nocast()
3 #define __nocast __attribute__((nocast)) macro119 int __nocast obj, *ptr; in test_nocast()