[PATCH] D101053: [doc] Clarify constrained fcmps behavior

[Ulrich Weigand via Phabricator via llvm-commits]

uweigand accepted this revision.
uweigand added a comment.
This revision is now accepted and ready to land.

B.t.w. even if the raised exception does cause an actual trap, the result of the instruction might _still_ be accessed.  This is now of course platform-specific, but e.g. on Linux it is possible to inspect the result of the instruction in the trap handler if one is installed; it is also possible for the trap handler to resume execution so that the result may also still be used by the original code afterwards.  In those cases, even if there is a trap, there would still be difference between fcmp and fcmps visible.

But in any case, I guess if this extra text clarifies things for you, it might also be helpful to others, so I certainly don't mind adding it.


Repository:
  rG LLVM Github Monorepo

CHANGES SINCE LAST ACTION
  https://reviews.llvm.org/D101053/new/

https://reviews.llvm.org/D101053