Hi! During a previous patch review, Segher asked that I provide better
messages when builtins are unavailable because they require both a minimum
CPU and the enablement of VSX instructions. This patch does just that.
Bootstrapped and tested on powerpc64le-linux-gnu with no regressions.
Is this okay for trunk?
Thanks!
Bill
2021-11-11 Bill Schmidt <wschm...@linux.ibm.com>
gcc/
* config/rs6000/rs6000-call.c (rs6000_invalid_new_builtin): Change
error messages for ENB_P8V and ENB_P9V.
---
gcc/config/rs6000/rs6000-call.c | 6 ++++--
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git a/gcc/config/rs6000/rs6000-call.c b/gcc/config/rs6000/rs6000-call.c
index 85fec80c6d7..035266eb001 100644
--- a/gcc/config/rs6000/rs6000-call.c
+++ b/gcc/config/rs6000/rs6000-call.c
@@ -11943,7 +11943,8 @@ rs6000_invalid_new_builtin (enum rs6000_gen_builtins
fncode)
error ("%qs requires the %qs option", name, "-mcpu=power8");
break;
case ENB_P8V:
- error ("%qs requires the %qs option", name, "-mpower8-vector");
+ error ("%qs requires the %qs and %qs options", name, "-mcpu=power8",
+ "-mvsx");
break;
case ENB_P9:
error ("%qs requires the %qs option", name, "-mcpu=power9");
@@ -11953,7 +11954,8 @@ rs6000_invalid_new_builtin (enum rs6000_gen_builtins
fncode)
name, "-mcpu=power9", "-m64", "-mpowerpc64");
break;
case ENB_P9V:
- error ("%qs requires the %qs option", name, "-mpower9-vector");
+ error ("%qs requires the %qs and %qs options", name, "-mcpu=power9",
+ "-mvsx");
break;
case ENB_IEEE128_HW:
error ("%qs requires ISA 3.0 IEEE 128-bit floating point", name);
--
2.27.0
