-
Philippe Gerum authored
This abstraction is overkill and logically wrong. What we want is two mutually convertible types: - a portable base type which is wide enough for representing a set of bitwise conditions/statuses. Therefore, this type still has to be 32bit wide at most nowadays. - another type which can be used with atomic operations on any platform, typically a long integer type. We drop xnflags_t, replacing it with a basic int type in function prototypes, or long integer type when atomic operations are involved internally. At any rate, atomic operations will produce significant results for us only for the first 32 LSBs of such word.
575c762a