efriedma-quic wrote: We don't really specify what, exactly, the consequences are for violating noalias in LangRef. But... we do say elsewhere "If memory accesses alias even though they are noalias according to !tbaa metadata, the behavior is undefined." Probably the same has to apply to noalias, or else we get weird consequences for optimization.
I mean, in practice a lot of the optimizations you'd actually want to do would be fine with "load produces an indeterminate value, store stores an indeterminate value". But we don't distinguish those optimizations from the ones that actually do loudly blow up (like rematerializing a load). https://github.com/llvm/llvm-project/pull/136792 _______________________________________________ cfe-commits mailing list cfe-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
