| commit | 8d2793ef6b15dbdd347c854f663eb145af5ee593 | |
| author | Marek Polacek <polacek@redhat.com> | |
| Thu, 9 Mar 2023 23:43:34 +0000 (9 18:43 -0500) | ||
| committer | Marek Polacek <polacek@redhat.com> | |
| Mon, 1 May 2023 21:50:28 +0000 (1 17:50 -0400) | ||
| tree | 3f758a429a5bf606f9e6f6de1a771a9185287e9f | treesnapshot (tar.gz zip) |
| parent | 07c52d1eec9671af92b7ce977b469f13a87887ad | commitdiff |
ubsan: ubsan_maybe_instrument_array_ref tweak
In <https://gcc.gnu.org/pipermail/gcc-patches/2023-March/613687.html>
we discussed that the copy_node in ubsan_maybe_instrument_array_ref
is redundant, but also that it'd be best to postpone the optimization
to GCC 14. So I'm making that change now.
gcc/c-family/ChangeLog:
* c-ubsan.cc (ubsan_maybe_instrument_array_ref): Don't copy_node.
In <https://gcc.gnu.org/pipermail/gcc-patches/2023-March/613687.html>
we discussed that the copy_node in ubsan_maybe_instrument_array_ref
is redundant, but also that it'd be best to postpone the optimization
to GCC 14. So I'm making that change now.
gcc/c-family/ChangeLog:
* c-ubsan.cc (ubsan_maybe_instrument_array_ref): Don't copy_node.
| gcc/c-family/c-ubsan.cc | diffblobblamehistory |