aboutsummaryrefslogtreecommitdiff
path: root/gcc/selftest.h
diff options
context:
space:
mode:
authorKewen Lin <linkw@linux.ibm.com>2023-01-18 02:34:19 -0600
committerKewen Lin <linkw@linux.ibm.com>2023-01-18 02:34:19 -0600
commit5d9529687deb9ed009361a16c02a7f6c3e2ebbf3 (patch)
tree8f7e5f09a53b86b43b47b9397b8d079815678ece /gcc/selftest.h
parent159b0f41adc4c8ead45e12a523470381ce716ff2 (diff)
downloadgcc-5d9529687deb9ed009361a16c02a7f6c3e2ebbf3.zip
gcc-5d9529687deb9ed009361a16c02a7f6c3e2ebbf3.tar.gz
gcc-5d9529687deb9ed009361a16c02a7f6c3e2ebbf3.tar.bz2
rs6000: Teach rs6000_opaque_type_invalid_use_p about gcall [PR108348]
PR108348 shows one special case that MMA opaque types are used in function arguments and treated as pass by reference, it results in one copying from argument to a temp variable, since this copying happens before rs6000_function_arg check, it can cause ICE without MMA support then. This patch is to teach function rs6000_opaque_type_invalid_use_p to check if any function argument in a gcall stmt has the invalid use of MMA opaque types. btw, I checked the handling on return value, it doesn't have this kind of issue as its checking and error emission is quite early, so this doesn't handle function return value. PR target/108348 gcc/ChangeLog: * config/rs6000/rs6000.cc (rs6000_opaque_type_invalid_use_p): Add the support for invalid uses of MMA opaque type in function arguments. gcc/testsuite/ChangeLog: * gcc.target/powerpc/pr108348-1.c: New test. * gcc.target/powerpc/pr108348-2.c: New test.
Diffstat (limited to 'gcc/selftest.h')
0 files changed, 0 insertions, 0 deletions