diff options
| author | Roger Sayle <roger@nextmovesoftware.com> | 2022-07-19 08:39:43 +0100 |
|---|---|---|
| committer | Roger Sayle <roger@nextmovesoftware.com> | 2022-07-19 08:39:43 +0100 |
| commit | 40f6e5912288256ee8ac41474f2dce7b6881c111 (patch) | |
| tree | 2c726cfe0fe286f170b53b31fc5b6917f3d8882e /gcc/cp/cp-objcp-common.cc | |
| parent | 2180cdd8a0e65c2790a7732c82de87f83478487b (diff) | |
| download | gcc-40f6e5912288256ee8ac41474f2dce7b6881c111.zip gcc-40f6e5912288256ee8ac41474f2dce7b6881c111.tar.gz gcc-40f6e5912288256ee8ac41474f2dce7b6881c111.tar.bz2 | |
PR c/106264: Silence warnings from __builtin_modf et al.
This middle-end patch resolves PR c/106264 which is a spurious warning
regression caused by the tree-level expansion of modf, frexp and remquo
producing "expression has no-effect" when the built-in function's result
is ignored. When these built-ins were first expanded at tree-level,
fold_builtin_n would blindly set TREE_NO_WARNING for all built-ins. Now
that we're more discerning, we should precisely call suppress_warning
selectively on those COMPOUND_EXPRs that need them.
2022-07-19 Roger Sayle <roger@nextmovesoftware.com>
Richard Biener <rguenther@suse.de>
gcc/ChangeLog
PR c/106264
* builtins.cc (fold_builtin_frexp): Call suppress_warning on
COMPOUND_EXPR to silence spurious warning if result isn't used.
(fold_builtin_modf): Likewise.
(do_mpfr_remquo): Likewise.
gcc/testsuite/ChangeLog
PR c/106264
* gcc.dg/pr106264.c: New test case.
Diffstat (limited to 'gcc/cp/cp-objcp-common.cc')
0 files changed, 0 insertions, 0 deletions