subject:"\[Bug libstdc\+\+\/98001\] ext\/stdio_filebuf\/char\/79820.cc is broken"

[Bug libstdc++/98001] ext/stdio_filebuf/char/79820.cc is broken

2020-11-26 Thread redi at gcc dot gnu.org via Gcc-bugs

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98001 Jonathan Wakely changed: What|Removed |Added Resolution|--- |FIXED Target Milestone|---

[Bug libstdc++/98001] ext/stdio_filebuf/char/79820.cc is broken

2020-11-26 Thread cvs-commit at gcc dot gnu.org via Gcc-bugs

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98001 --- Comment #9 from CVS Commits --- The releases/gcc-8 branch has been updated by Jonathan Wakely : https://gcc.gnu.org/g:c6145860aac6acfeed2a98fe7532dd2cd0ffab2b commit r8-10650-gc6145860aac6acfeed2a98fe7532dd2cd0ffab2b Author: Jonathan Wakely

[Bug libstdc++/98001] ext/stdio_filebuf/char/79820.cc is broken

2020-11-26 Thread cvs-commit at gcc dot gnu.org via Gcc-bugs

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98001 --- Comment #8 from CVS Commits --- The releases/gcc-9 branch has been updated by Jonathan Wakely : https://gcc.gnu.org/g:e45e65016754cf4bfc6c00cbbdca700f01f7c324 commit r9-9074-ge45e65016754cf4bfc6c00cbbdca700f01f7c324 Author: Jonathan Wakely

[Bug libstdc++/98001] ext/stdio_filebuf/char/79820.cc is broken

2020-11-26 Thread cvs-commit at gcc dot gnu.org via Gcc-bugs

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98001 --- Comment #7 from CVS Commits --- The releases/gcc-10 branch has been updated by Jonathan Wakely : https://gcc.gnu.org/g:4cdc67405842946e08e7ddf375e850331530abb7 commit r10-9087-g4cdc67405842946e08e7ddf375e850331530abb7 Author: Jonathan Wakel

[Bug libstdc++/98001] ext/stdio_filebuf/char/79820.cc is broken

2020-11-26 Thread redi at gcc dot gnu.org via Gcc-bugs

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98001 --- Comment #6 from Jonathan Wakely --- I added b.close() before the fclose anyway. I'll backport this.

[Bug libstdc++/98001] ext/stdio_filebuf/char/79820.cc is broken

2020-11-26 Thread cvs-commit at gcc dot gnu.org via Gcc-bugs

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98001 --- Comment #5 from CVS Commits --- The master branch has been updated by Jonathan Wakely : https://gcc.gnu.org/g:2762cb1df686fc1ebcee23c7c4f0f6e8bf5a6abc commit r11-5437-g2762cb1df686fc1ebcee23c7c4f0f6e8bf5a6abc Author: Jonathan Wakely Date:

[Bug libstdc++/98001] ext/stdio_filebuf/char/79820.cc is broken

2020-11-26 Thread redi at gcc dot gnu.org via Gcc-bugs

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98001 --- Comment #4 from Jonathan Wakely --- Yes, when the filebuf is given a FILE* it doesn't own it, and so the destructor doesn't touch it: __basic_file* __basic_file::close() { __basic_file* __ret = static_cast<__basic_file*>(NULL);

[Bug libstdc++/98001] ext/stdio_filebuf/char/79820.cc is broken

2020-11-26 Thread rguenther at suse dot de via Gcc-bugs

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98001 --- Comment #3 from rguenther at suse dot de --- On Thu, 26 Nov 2020, redi at gcc dot gnu.org wrote: > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98001 > > Jonathan Wakely changed: > >What|Removed |Added

[Bug libstdc++/98001] ext/stdio_filebuf/char/79820.cc is broken

2020-11-26 Thread redi at gcc dot gnu.org via Gcc-bugs

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98001 Jonathan Wakely changed: What|Removed |Added Assignee|unassigned at gcc dot gnu.org |redi at gcc dot gnu.org