diff options
| author | Jason Merrill <jason@redhat.com> | 2019-06-14 09:22:33 -0400 |
|---|---|---|
| committer | Jason Merrill <jason@gcc.gnu.org> | 2019-06-14 09:22:33 -0400 |
| commit | 8a26547b39e2e6ddc8097969c0a2c18f65afda6c (patch) | |
| tree | 87ddd732969e6b4939b31e88abc78bb954b1b796 /gcc/function.c | |
| parent | e748435795f8c6f3b77fa0ac18a43151a52ad324 (diff) | |
| download | gcc-8a26547b39e2e6ddc8097969c0a2c18f65afda6c.zip gcc-8a26547b39e2e6ddc8097969c0a2c18f65afda6c.tar.gz gcc-8a26547b39e2e6ddc8097969c0a2c18f65afda6c.tar.bz2 | |
PR c++/85552 - wrong instantiation of dtor for DMI.
The problem here is that when processing direct-initialization of a data
member, we don't need to worry about destruction semantics; that will be
handled in the [cd]tor. Conveniently, we already have tf_no_cleanup from a
similar fix to new-expressions.
* typeck2.c (digest_nsdmi_init): Set tf_no_cleanup for direct-init.
From-SVN: r272287
Diffstat (limited to 'gcc/function.c')
0 files changed, 0 insertions, 0 deletions