aboutsummaryrefslogtreecommitdiff
path: root/gcc/function.cc
diff options
context:
space:
mode:
authorJakub Jelinek <jakub@redhat.com>2022-04-01 11:49:40 +0200
committerJakub Jelinek <jakub@redhat.com>2022-04-01 11:49:40 +0200
commite0ce885851dfd926c0cfe6f23a2debc87ea2bb9d (patch)
tree5e7e90f55a2c75ab8f54e068550e69a0c4458213 /gcc/function.cc
parent215c8c5826c688eaebce4d9cd0d52e9da7bc208f (diff)
downloadgcc-e0ce885851dfd926c0cfe6f23a2debc87ea2bb9d.zip
gcc-e0ce885851dfd926c0cfe6f23a2debc87ea2bb9d.tar.gz
gcc-e0ce885851dfd926c0cfe6f23a2debc87ea2bb9d.tar.bz2
testsuite: Add further zero size elt passing tests [PR102024]
As discussed in PR102024, zero width bitfields might not be the only ones causing ABI issues at least on mips, zero size arrays or (in C only) zero sized (empty) structures can be problematic too. The following patch adds some coverage for it too. Tested on x86_64-linux with make check-gcc check-g++ RUNTESTFLAGS='ALT_CC_UNDER_TEST=gcc ALT_CXX_UNDER_TEST=g++ --target_board=unix\{-m32,-m64\} compat.exp=pr102024*' make check-gcc check-g++ RUNTESTFLAGS='ALT_CC_UNDER_TEST=clang ALT_CXX_UNDER_TEST=clang++ --target_board=unix\{-m32,-m64\} compat.exp=pr102024*' with gcc/g++ 10.3 and clang 11. Everything but (expectedly) FAIL: gcc.dg/compat/pr102024 c_compat_x_tst.o-c_compat_y_alt.o execute FAIL: gcc.dg/compat/pr102024 c_compat_x_alt.o-c_compat_y_tst.o execute for -m64 ALT_CC_UNDER_TEST=gcc passes. 2022-04-01 Jakub Jelinek <jakub@redhat.com> PR target/102024 * gcc.dg/compat/pr102024_test.h: Add further tests with zero sized structures and arrays. * g++.dg/compat/pr102024_test.h: Add further tests with zero sized arrays.
Diffstat (limited to 'gcc/function.cc')
0 files changed, 0 insertions, 0 deletions