aboutsummaryrefslogtreecommitdiff
path: root/gcc/tree-ssa-loop-ivopts.c
diff options
context:
space:
mode:
authorAndreas Krebbel <krebbel@linux.vnet.ibm.com>2015-05-19 17:41:21 +0000
committerAndreas Krebbel <krebbel@gcc.gnu.org>2015-05-19 17:41:21 +0000
commitcb4c41dd4d9b0cf349e9c51c23492113dea975a6 (patch)
tree452095ebe18ef24556b523eeac0cf483a5c18e3b /gcc/tree-ssa-loop-ivopts.c
parent17521813e152860e7cfa5a5d0255cf2ca5e704be (diff)
downloadgcc-cb4c41dd4d9b0cf349e9c51c23492113dea975a6.zip
gcc-cb4c41dd4d9b0cf349e9c51c23492113dea975a6.tar.gz
gcc-cb4c41dd4d9b0cf349e9c51c23492113dea975a6.tar.bz2
S/390 Invalid vector binary ops
This is a first try to implement at least some of the requirements regarding the vector bool type documented for IBM XLC. With this patch error messages will be issued for invalid uses of vector bool types in binary operators. vector bool types are being marked opaque in order to prevent the front-end from complaining about "vector bool long" vs "vector bool long long" combinations on 64 bit. The opaque flag basically suppresses any type checking. However, we still want vector bool to be accepted only in contexts specified in the documentation (to be published soon). Implementing the invalid binary op hook does this for binary operators at least. But this is far from being complete :( gcc/ * config/s390/s390.c (s390_vector_bool_type_p): New function. (s390_invalid_binary_op): New function. (TARGET_INVALID_BINARY_OP): Define macro. From-SVN: r223404
Diffstat (limited to 'gcc/tree-ssa-loop-ivopts.c')
0 files changed, 0 insertions, 0 deletions