diff options
| author | Marko Mäkelä <marko.makela@mariadb.com> | 2019-03-12 12:55:38 +0200 |
|---|---|---|
| committer | Marko Mäkelä <marko.makela@mariadb.com> | 2019-03-12 13:03:20 +0200 |
| commit | 32de60bb2e9f06b24c76fc41bef81e35c14ca528 (patch) | |
| tree | 5ae55db6951a61a117c34ff27a3a56a18720b607 /tests | |
| parent | ea52ecbc103b1424cf0b6f8faf990676b2b57a63 (diff) | |
| download | mariadb-git-32de60bb2e9f06b24c76fc41bef81e35c14ca528.tar.gz | |
MDEV-18749: Fix GCC -flifetime-dse
row_merge_create_fts_sort_index(): Initialize dict_col_t in
an unambiguous way. GCC 6 and later appear to be able to optimize
away the memset() that is part of mem_heap_zalloc() in the
placement new call. Let us avoid using placement new in order
to ensure that the objects will actually be initialized.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71388
https://gcc.gnu.org/ml/gcc/2016-02/msg00207.html
While the latter reference hints that the optimization is only
applicable to non-POD types (and dict_col_t does not define
any member functions before 10.2), it is most consistent to
use the same initialization across all versions.
Diffstat (limited to 'tests')
0 files changed, 0 insertions, 0 deletions