[Bug lto/82172] Destruction of basic_string in basic_stringbuf::overflow with _GLIBCXX_USE_CXX11_ABI=0, -flto, and C++17 mode results in invalid delete

2018-09-20 Thread dave.gittins at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82172 --- Comment #26 from Gubbins --- If anyone is interested, I received the following response on my bug report with Apple. > This issue behaves as intended based on the following: > > The program produced by ld64 seems fine: > > [/tmp/35663253]>

[Bug lto/82172] Destruction of basic_string in basic_stringbuf::overflow with _GLIBCXX_USE_CXX11_ABI=0, -flto, and C++17 mode results in invalid delete

2018-09-20 Thread dave.gittins at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82172 --- Comment #27 from Gubbins --- > Dave, the fix for PR 86138 might also fix this case for Darwin - could you > check that please? I can confirm that using my homebrew-installed gcc 8.2.0 package on OSX, the issue no longer occurs. I don't know

[Bug lto/82172] Destruction of basic_string in basic_stringbuf::overflow with _GLIBCXX_USE_CXX11_ABI=0, -flto, and C++17 mode results in invalid delete

2017-09-27 Thread dave.gittins at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82172 Gubbins changed: What|Removed |Added CC||dave.gittins at gmail dot com --- Comment #19

[Bug lto/82172] Destruction of basic_string in basic_stringbuf::overflow with _GLIBCXX_USE_CXX11_ABI=0, -flto, and C++17 mode results in invalid delete

2017-09-27 Thread dave.gittins at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82172 --- Comment #21 from Gubbins --- (In reply to Martin Liška from comment #20) > Your failure happens even w/o LTO, am I right? > But yes, the problem looks very similar to what happens for ld.bfd. You are right. Does anyone know how I would rais

[Bug lto/82172] Destruction of basic_string in basic_stringbuf::overflow with _GLIBCXX_USE_CXX11_ABI=0, -flto, and C++17 mode results in invalid delete

2017-11-21 Thread dave.gittins at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82172 --- Comment #24 from Gubbins --- > > Does anyone know how I would raise this with someone who can fix it on the > > Darwin side? Or could it be worked around by gcc? > > Linker should provide precise information to GCC. FWIW, I have raised a bu

[Bug c++/55805] Empty brace-init-list causes warning "missing initializer for member" in C++11

2015-06-15 Thread dave.gittins at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=55805 Gubbins changed: What|Removed |Added CC||dave.gittins at gmail dot com --- Comment #2

[Bug c++/55805] Empty brace-init-list causes warning "missing initializer for member" in C++11

2015-06-16 Thread dave.gittins at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=55805 --- Comment #5 from Gubbins --- (In reply to Jonathan Wakely from comment #4) > (In reply to Gubbins from comment #2) > > Therefore no field initializers are involved. The warning in this situation > > is surely incorrect? I think the original bu

[Bug c++/55805] Empty brace-init-list causes warning "missing initializer for member" in C++11

2015-06-16 Thread dave.gittins at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=55805 --- Comment #6 from Gubbins --- (In reply to Jonathan Wakely from comment #3) > (In reply to Gubbins from comment #2) > > The original bug report points that in C++11 this is *not* aggregate > > initialization, but is in fact value initialization

[Bug c++/55805] Empty brace-init-list causes warning "missing initializer for member" in C++11

2015-06-16 Thread dave.gittins at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=55805 --- Comment #7 from Gubbins --- (In reply to Gubbins from comment #6) > (In reply to Jonathan Wakely from comment #3) > > (In reply to Gubbins from comment #2) > > > The original bug report points that in C++11 this is *not* aggregate > > > initi

[Bug c++/55805] Empty brace-init-list causes warning "missing initializer for member" in C++11

2015-06-16 Thread dave.gittins at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=55805 --- Comment #9 from Gubbins --- (In reply to Jonathan Wakely from comment #8) > (In reply to Gubbins from comment #5) > > The warning is still produced with gcc 4.9.2 (surely that's supported?) > > The warning isn't given for 5.1 and trunk (not

[Bug c++/55805] Empty brace-init-list causes warning "missing initializer for member" in C++11

2015-06-16 Thread dave.gittins at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=55805 --- Comment #11 from Gubbins --- (In reply to Jonathan Wakely from comment #10) > (In reply to Gubbins from comment #9) > > I see, thanks. Will there be no more releases on the 4.9 branch? > > There will be more. https://gcc.gnu.org/ml/gcc/2015-