[Bug libstdc++/54289] New: setjmp isn't included into std namespace

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54289 Bug #: 54289 Summary: setjmp isn't included into std namespace Classification: Unclassified Product: gcc Version: 4.6.1 Status: UNCONFIRMED Severity: normal Priority:

[Bug libstdc++/54289] setjmp isn't included into std namespace

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54289 --- Comment #4 from Dmitry 2012-08-16 19:43:15 UTC --- Sorry, but I think standard declares that all function should be in std.

[Bug libstdc++/54289] setjmp isn't included into std namespace

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54289 --- Comment #6 from Dmitry 2012-08-16 19:49:27 UTC --- I think standard of C std libs declares setjmp as a function. So, it should be function. Some code: __BEGIN_NAMESPACE_STD typedef struct __jmp_buf_tag jmp_buf[1]; extern int setjmp (jmp_bu

[Bug libstdc++/54289] setjmp isn't included into std namespace

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54289 --- Comment #9 from Dmitry 2012-08-16 19:55:57 UTC --- C standard: The header defines the macro setjmp, and declares one function and one type, for bypassing the normal function call and return discipline. OK. I agree with you. But one moment.

[Bug c++/58308] Segmentation fault: internal compiler error: in make_decl_rtl, at varasm.c:1147

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58308 --- Comment #1 from Dmitry --- c++11 mode is used

[Bug c++/58308] New: Segmentation fault: internal compiler error: in make_decl_rtl, at varasm.c:1147

: minor Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: dmitriy-hshg at mail dot ru Next code causes GCC 4.7.3 to fail, it should report problem. int main() { int x = 666; struct A { int *p = &x; } a; } T

[Bug c++/58629] New: Do not implicit move instance for throw operator

: c++ Assignee: unassigned at gcc dot gnu.org Reporter: dmitriy-hshg at mail dot ru Created attachment 30959 --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=30959&action=edit Example It is good idea to use move semantics for throw operator: std::runtime_erro

[Bug c++/57533] When throwing local variable, it's being move-constructed even if not going out of scope.

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57533 Dmitry changed: What|Removed |Added CC||dmitriy-hshg at mail dot ru --- Comment #2 from

[Bug c++/58629] Do not implicit move instance for throw operator

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58629 Dmitry changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|---