[Bug c++/69814] New: internal compiler error: Segmentation fault on Template Meta Programming

2016-02-13 Thread wingfire at gmail dot com
Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: wingfire at gmail dot com Target Milestone: --- Created attachment 37684 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=37684&action=edit Preprocessed file g++ versio

[Bug c++/69812] New: internal compiler error: Segmentation fault on Template Meta Programming

2016-02-13 Thread wingfire at gmail dot com
Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: wingfire at gmail dot com Target Milestone: --- Created attachment 37683 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=37683&action=edit Preprocessed file g++ versio

[Bug c++/54590] Incorrect multi-inheritence bases layout

2012-09-16 Thread wingfire at gmail dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54590 Sun, Chaoyang changed: What|Removed |Added Status|RESOLVED|UNCONFIRMED Resolution|INVALID

[Bug c++/54590] Incorrect multi-inheritence bases layout

2012-09-16 Thread wingfire at gmail dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54590 --- Comment #2 from Sun, Chaoyang 2012-09-16 11:38:24 UTC --- (In reply to comment #1) > The first word contains a pointer to the vtable for X. If the first word is the vtable of X, the memory layout should be: { vptr of x; data of B; vptr of A;

[Bug c++/54590] New: Incorrect multi-inheritence bases layout

2012-09-15 Thread wingfire at gmail dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54590 Bug #: 54590 Summary: Incorrect multi-inheritence bases layout Classification: Unclassified Product: gcc Version: 4.7.1 Status: UNCONFIRMED Severity: major Priority: