================
@@ -7646,6 +7646,17 @@ def J : JoinedOrSeparate<["-"], "J">,
let Visibility = [FC1Option] in {
+def ffp_maxmin_behavior_EQ
+ : Joined<["-"], "ffp-maxmin-behavior=">,
+ Flags<[HelpHidden]>,
+ Group<f_Group>,
+ Values<"legacy,portable,extremum,extremenum">,
+ HelpText<"Control MAX/MIN and [max|min][loc|val] behavior: "
+ "legacy (cmp+select), portable (same as legacy, "
+ " but may use max/minNum when -fno-signed-zeros "
+ "-fno-honor-nans), extremum (IEEE-754-2019 maximum/minimum), "
+ "extremenum (IEEE-754-2008 max/minNum)">;
----------------
tarunprabhu wrote:
Do you know if the terms `extremum` and `extremenum` are "effectively
standard"? I had to look closely to see the difference. They do make sense to
me, it's just that they are so close to one another that I can see users making
a mistake fairly easily. I was just wondering if there might be a different
name one could use here.
https://github.com/llvm/llvm-project/pull/184730
_______________________________________________
cfe-commits mailing list
[email protected]
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
