public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ldionne.2 at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/59498] New: Pack expansion error in template alias Date: Fri, 13 Dec 2013 18:34:00 -0000 [thread overview] Message-ID: <bug-59498-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59498 Bug ID: 59498 Summary: Pack expansion error in template alias Product: gcc Version: 4.9.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: ldionne.2 at gmail dot com GCC Version ----------- gcc-4.9 (GCC) 4.9.0 20131201 (experimental) Installed with Homebrew. System ------ OS X 10.8.5 Command line to trigger the bug ------------------------------- gcc-4.9 -std=c++11 -Wall -Wextra -pedantic -o /dev/null -c template_alias_bug.cpp Minimal code to reproduce ------------------------- template <typename T, typename ...> using alias = T; template <typename ...T> using variadic_alias = alias<T...>; using Fail = variadic_alias<int>; int main() { } Error message ------------- template_alias_bug.cpp:9:34: error: pack expansion argument for non-pack parameter 'T' of alias template 'template<class T, class ...> using alias = T' using variadic_alias = alias<T...>; ^ template_alias_bug.cpp:5:11: note: declared here template <typename T, typename ...> ^ template_alias_bug.cpp:11:14: error: expected type-specifier before 'variadic_alias' using Fail = variadic_alias<int>; ^ Possibly related ---------------- Bug 58856 Comments -------- Clang compiles the code just fine and I don't see any obvious reason why that would be invalid C++11 (I could be mistaken), so I think that's a GCC bug.
next reply other threads:[~2013-12-13 18:34 UTC|newest] Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-12-13 18:34 ldionne.2 at gmail dot com [this message] 2014-05-04 3:34 ` [Bug c++/59498] " rscrihf at gmail dot com 2014-05-04 11:41 ` [Bug c++/59498] [4.9/4.10 Regression] " redi at gcc dot gnu.org 2014-05-26 14:02 ` rguenth at gcc dot gnu.org 2014-05-29 18:10 ` jason at gcc dot gnu.org 2014-06-03 12:21 ` [Bug c++/59498] [DR 1430][4.9/4.10 " jason at gcc dot gnu.org 2014-07-16 13:31 ` jakub at gcc dot gnu.org 2014-07-27 14:31 ` ldionne.2 at gmail dot com 2014-07-27 15:01 ` ldionne.2 at gmail dot com 2014-10-30 10:42 ` [Bug c++/59498] [DR 1430][4.9/5 " jakub at gcc dot gnu.org 2014-12-12 4:15 ` jason at gcc dot gnu.org 2015-06-26 20:10 ` [Bug c++/59498] [DR 1430][4.9/5/6 " jakub at gcc dot gnu.org 2015-06-26 20:35 ` jakub at gcc dot gnu.org 2021-05-14 9:47 ` [Bug c++/59498] [DR 1430][9/10/11/12 " jakub at gcc dot gnu.org 2021-06-01 8:06 ` rguenth at gcc dot gnu.org 2022-05-27 9:12 ` [Bug c++/59498] [DR 1430][9/10/11/12/13 " rguenth at gcc dot gnu.org 2022-05-27 9:12 ` [Bug c++/59498] [DR 1430][10/11/12/13 " rguenth at gcc dot gnu.org 2022-06-28 10:30 ` jakub at gcc dot gnu.org 2023-03-27 15:30 ` pinskia at gcc dot gnu.org 2023-03-29 16:49 ` ncm at cantrip dot org 2023-07-07 10:30 ` [Bug c++/59498] [DR 1430][11/12/13/14 " rguenth at gcc dot gnu.org
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-59498-4@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).