> Dispatching to per-type functions (instead of per-size ones) is mere busy work Having a function per each supported size plus one for emulated locking is still safer than having a pair, where one deals with opaque data type.
> all that code is generated and implementation specific, not user visible It is visible. https://llvm.org/docs/Atomics.html ("libcalls" section) https://gcc.gnu.org/wiki/Atomic/GCCMM/LIbrary ("The library interface" section) Having a clear and reasonable error messages is reasonable as well. This is easier to implement it at compiler site.
_______________________________________________ Tinycc-devel mailing list [email protected] https://lists.nongnu.org/mailman/listinfo/tinycc-devel
