[Bug c++/53305] New: internal crash with variadic templates and decltype

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53305 Bug #: 53305 Summary: internal crash with variadic templates and decltype Classification: Unclassified Product: gcc Version: 4.6.3 Status: UNCONFIRMED Severity: normal

[Bug c++/53307] New: internal crash with variadic templates and decltype

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53307 Bug #: 53307 Summary: internal crash with variadic templates and decltype Classification: Unclassified Product: gcc Version: 4.8.0 Status: UNCONFIRMED Severity: major

[Bug c++/53307] internal crash with variadic templates and decltype

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53307 chesstr at hotmail dot com changed: What|Removed |Added Severity|major |normal

[Bug c++/53307] internal crash with variadic templates and decltype

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53307 chesstr at hotmail dot com changed: What|Removed |Added Attachment #27363|0 |1 is obsolete

[Bug c++/53307] internal crash with variadic templates and decltype

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53307 --- Comment #2 from chesstr at hotmail dot com 2012-05-10 20:09:44 UTC --- Comment on attachment 27366 --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=27366 better test case >#include >template struct tuple{}; > &

[Bug c++/53307] internal crash with variadic templates and decltype

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53307 --- Comment #3 from chesstr at hotmail dot com 2012-05-10 20:57:25 UTC --- Therefore, it seems that 0 length argument packs are not handled correctly in decltype.

[Bug c++/53311] New: [C++0x] argument packs are not handled correctly in decltype

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53311 Bug #: 53311 Summary: [C++0x] argument packs are not handled correctly in decltype Classification: Unclassified Product: gcc Version: 4.8.0 Status: UNCONFIRMED

[Bug c++/53311] [C++0x] argument packs are not handled correctly in decltype

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53311 chesstr at hotmail dot com changed: What|Removed |Added Attachment #27368|0 |1 is obsolete

[Bug c++/53648] New: nested empty tuple

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53648 Bug #: 53648 Summary: nested empty tuple Classification: Unclassified Product: gcc Version: 4.8.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component

[Bug libstdc++/53648] [C++11] nested empty tuples

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53648 --- Comment #2 from chesstr at hotmail dot com 2012-06-12 17:13:33 UTC --- (In reply to comment #1) > I have a fix for this already, IIRC it's simply a case of not using the EBO > for > a tuple that contains std::tuple<>

[Bug libstdc++/53648] [C++11] nested empty tuples

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53648 --- Comment #4 from chesstr at hotmail dot com 2012-06-12 18:03:56 UTC --- (In reply to comment #3) > There are other cases involving non-empty tuples that will still result in an > ambiguity e.g. > > struct A { }; > auto d