diff options
author | Jakub Jelinek <jakub@redhat.com> | 2023-09-29 11:23:16 +0200 |
---|---|---|
committer | Jakub Jelinek <jakub@redhat.com> | 2023-09-29 11:23:16 +0200 |
commit | 59cda1f9525702d5d6560002c874f12c0103f7df (patch) | |
tree | 4d917f72ce53bc4d47fcd812053eeff9153fe3c6 /gcc/function.h | |
parent | 7525707c5f3edb46958c4fdfbe30de5ddfa8923a (diff) | |
download | gcc-59cda1f9525702d5d6560002c874f12c0103f7df.zip gcc-59cda1f9525702d5d6560002c874f12c0103f7df.tar.gz gcc-59cda1f9525702d5d6560002c874f12c0103f7df.tar.bz2 |
use *_grow_cleared rather than *_grow on vect_unpromoted_value
vect_recog_over_widening_pattern is another spot which triggers the
right now commented out static assertion in vec.h which asserts
{quick,safe}_grow vec operations are only used with trivially default
constructible types.
I had a look at this and I think using quick_grow_cleared is best choice
here. The nops is 2 or 1 most of the time, worst case 3, so the price of
extra initialization of 4 pointer-sized-or-less members times 1, 2 or 3
doesn't seem worth bothering, it is similar to the bitmap_head case where
we already pay the price for just one structure anytime we do
vect_unpromoted_value unprom_diff;
(and later set_op on it) or even
vect_unpromoted_value unprom0[2];
With this patch and Richard S's poly_int_pod removal the static_assert can
be enabled as well and gcc builds.
2023-09-29 Jakub Jelinek <jakub@redhat.com>
* tree-vect-patterns.cc (vect_recog_over_widening_pattern): Use
quick_grow_cleared method on unprom rather than quick_grow.
Diffstat (limited to 'gcc/function.h')
0 files changed, 0 insertions, 0 deletions