efriedma-quic wrote: Should this be part of the "memory" attribute, instead of an independent thing?
In my head, the model I have is the following: the current fp state is a bit of thread-local state, and transforms that use generic reasoning about memory reads/writes should be able to conservatively handle fp state without knowing anything about it. Then we have some additional markings that allow fp-aware transforms to be more precise: they can see if the operation reads the status flags, or whether the rounding mode is known. I don't think attributes specific to intrinsics make sense in this context; anything that makes sense to assert about an intrinsic call, equally makes sense to assert about a non-intrinsic call. https://github.com/llvm/llvm-project/pull/122313 _______________________________________________ llvm-branch-commits mailing list llvm-branch-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-branch-commits
