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
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.
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
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
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87493
Vinícius dos Santos Oliveira changed:
What|Removed |Added
Status|WAITING |RESOLVED
Resoluti
++
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
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
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
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
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
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98449
Vinícius dos Santos Oliveira changed:
What|Removed |Added
Status|SUSPENDED |RESOLVED
Resoluti
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
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
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98449
Vinícius dos Santos Oliveira changed:
What|Removed |Added
CC||vini.ipsmaker at gmail
14 matches
Mail list logo