aboutsummaryrefslogtreecommitdiff
path: root/gcc/doc/cppopts.texi
diff options
context:
space:
mode:
authorAlexandre Oliva <oliva@adacore.com>2023-02-22 14:35:20 -0300
committerAlexandre Oliva <oliva@gnu.org>2023-02-22 14:38:17 -0300
commit1a45573d3d7b0098116f4ccde5d9be5d32b5653a (patch)
tree737e7c6283c1c42a7ad1aa8734c237ff30f82917 /gcc/doc/cppopts.texi
parentd70f49e98245f80fcf8b2e68a9f06955f52e1de7 (diff)
downloadgcc-1a45573d3d7b0098116f4ccde5d9be5d32b5653a.zip
gcc-1a45573d3d7b0098116f4ccde5d9be5d32b5653a.tar.gz
gcc-1a45573d3d7b0098116f4ccde5d9be5d32b5653a.tar.bz2
testsuite: Accept pmf-vbit-in-delta extra warning
cp_build_binary_op, that issues -Waddress warnings, issues an extra warning on arm targets, that g++.dg/warn/Waddress-5.C does not expect when comparing a pointer-to-member-function literal with null. The reason for the extra warning is that, on arm targets, TARGET_PTRMEMFUNC_VBIT_LOCATION == ptrmemfunc_vbit_in_delta, which causes a different path to be taken, that extracts the pointer-to-function and the delta fields (minus the vbit) and compares each one with zero. It's when comparing this pointer-to-function with zero, in a recursive cp_build_binary_op, that another warning is issued. I suppose there should be a way to skip the warning in this recursive call, without disabling other warnings that might be issued there, but this patch only arranges for the test to tolerate the extra warning. for gcc/testsuite/ChangeLog * g++.dg/warn/Waddress-5.C: Tolerate extra -Waddress warning.
Diffstat (limited to 'gcc/doc/cppopts.texi')
0 files changed, 0 insertions, 0 deletions