[Bug c++/56914] New: internal compiler error: Segmentation fault

2013-04-10 Thread vini.ipsmaker at gmail dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56914 Bug #: 56914 Summary: internal compiler error: Segmentation fault Classification: Unclassified Product: gcc Version: 4.8.0 Status: UNCONFIRMED Severity: normal

[Bug c++/56914] internal compiler error: Segmentation fault

2013-04-10 Thread vini.ipsmaker at gmail dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56914 --- Comment #1 from Vinícius dos Santos Oliveira 2013-04-11 01:01:55 UTC --- Created attachment 29852 --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=29852 The preprocessed source file.

[Bug c++/56914] internal compiler error: Segmentation fault

2013-05-05 Thread vini.ipsmaker at gmail dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56914 --- Comment #5 from Vinícius dos Santos Oliveira 2013-05-05 18:32:14 UTC --- I tried to reproduce the bug today and nothing happened. I'm still using GCC 4.8.0, but my system changed a lot (ArchLinux is a rolling release distro) and I can't say w

[Bug libstdc++/87493] New: chrono::system_clock unusable with std::tm due to misaligned precisions

2018-10-02 Thread vini.ipsmaker at gmail dot com
Priority: P3 Component: libstdc++ Assignee: unassigned at gcc dot gnu.org Reporter: vini.ipsmaker at gmail dot com Target Milestone: --- This code doesn't work: std::tm cal_time; cal_time.tm_year = year; cal_time.tm_mon = month; cal_time.tm

[Bug libstdc++/87493] chrono::system_clock unusable with std::tm due to misaligned precisions

2018-10-03 Thread vini.ipsmaker at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87493 Vinícius dos Santos Oliveira changed: What|Removed |Added Status|WAITING |RESOLVED Resoluti

[Bug c++/66254] New: Member function shadowing enum classes

2015-05-22 Thread vini.ipsmaker at gmail dot com
++ Assignee: unassigned at gcc dot gnu.org Reporter: vini.ipsmaker at gmail dot com Target Milestone: --- Created attachment 35600 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=35600&action=edit The test code to trigger the error The attached code compiles fine on cla

[Bug libstdc++/98449] New: notify_all_at_thread_exit() should notify on cond while lock is held to avoid a race

2020-12-26 Thread vini.ipsmaker at gmail dot com via Gcc-bugs
Severity: normal Priority: P3 Component: libstdc++ Assignee: unassigned at gcc dot gnu.org Reporter: vini.ipsmaker at gmail dot com Target Milestone: --- Details of the issue can be found at: https://cplusplus.github.io/LWG/issue3343 I have a code base

[Bug libstdc++/108859] New: Exception thrown by std::filesystem::copy() is wrong

2023-02-20 Thread vini.ipsmaker at gmail dot com via Gcc-bugs
Component: libstdc++ Assignee: unassigned at gcc dot gnu.org Reporter: vini.ipsmaker at gmail dot com Target Milestone: --- std::filesystem::filesystem_error::path1() and std::filesystem::filesystem_error::path2() should contain the paths for the most deeply-nested call, not the

[Bug libstdc++/98449] [DR 3343] notify_all_at_thread_exit() should notify on cond while lock is held to avoid a race

2023-02-20 Thread vini.ipsmaker at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98449 --- Comment #3 from Vinícius dos Santos Oliveira --- LLVM's libcxx already applied this 1-line patchset: https://github.com/llvm/llvm-project/commit/64fc3cd55d586498dd21c5b3cfaa755793913772 Can we have the same here on GCC side (I've already sub

[Bug libstdc++/108861] New: notify_all_at_thread_exit() should notify on cond while lock is held to avoid a race

2023-02-20 Thread vini.ipsmaker at gmail dot com via Gcc-bugs
Severity: normal Priority: P3 Component: libstdc++ Assignee: unassigned at gcc dot gnu.org Reporter: vini.ipsmaker at gmail dot com Target Milestone: --- Created attachment 54493 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=54493&action=edit

[Bug libstdc++/98449] [DR 3343] notify_all_at_thread_exit() should notify on cond while lock is held to avoid a race

2023-02-20 Thread vini.ipsmaker at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98449 Vinícius dos Santos Oliveira changed: What|Removed |Added Status|SUSPENDED |RESOLVED Resoluti

[Bug libstdc++/108861] notify_all_at_thread_exit() should notify on cond while lock is held to avoid a race

2023-02-20 Thread vini.ipsmaker at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108861 --- Comment #2 from Vinícius dos Santos Oliveira --- > Isn't this just Bug 98449? Why did you close that as FIXED? Nobody is going to fix 98449. The ONE-line patchset fixing the issue was there for YEARS. Why does it take so many years to revie

[Bug libstdc++/108861] notify_all_at_thread_exit() should notify on cond while lock is held to avoid a race

2023-02-21 Thread vini.ipsmaker at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108861 --- Comment #5 from Vinícius dos Santos Oliveira --- > Because there is an open defect report against the C++ standard about this. > Basically until that is resolved, GCC's behavior is considered correct. How clueless of me to miss such obviou

[Bug libstdc++/98449] [DR 3343] notify_all_at_thread_exit() should notify on cond while lock is held to avoid a race

2021-07-09 Thread vini.ipsmaker at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98449 Vinícius dos Santos Oliveira changed: What|Removed |Added CC||vini.ipsmaker at gmail