public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pengujohn at xvlc dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/61382] New: parameter pack expansion unexpected order
Date: Sun, 01 Jun 2014 21:17:00 -0000 [thread overview]
Message-ID: <bug-61382-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61382
Bug ID: 61382
Summary: parameter pack expansion unexpected order
Product: gcc
Version: 4.9.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: pengujohn at xvlc dot de
Created attachment 32882
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=32882&action=edit
small example that expands like 3,2,1,0 ... should be 0,1,2,3
C++11 variadic templated parameter pack expansion happens for {}-initialiser in
reversed oder. As far as I understand this, they should be expanded in order. I
am not sure if its expansion or evaluation thats out of order.... clang++ does
the correct(?) ordering.
next reply other threads:[~2014-06-01 21:17 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-01 21:17 pengujohn at xvlc dot de [this message]
2014-06-01 22:27 ` [Bug c++/61382] " redi at gcc dot gnu.org
2014-06-03 23:03 ` thibaut.lutz at googlemail dot com
2014-06-04 8:50 ` thibaut.lutz at googlemail dot com
2014-06-04 15:51 ` jason at gcc dot gnu.org
2014-06-04 15:52 ` jason at gcc dot gnu.org
2014-06-11 21:35 ` pengujohn at xvlc dot de
2014-06-30 14:26 ` jason at gcc dot gnu.org
2014-07-03 2:02 ` brooks at gcc dot gnu.org
2014-07-03 3:37 ` brooks at gcc dot gnu.org
2014-07-03 8:29 ` jakub at gcc dot gnu.org
2014-07-04 7:24 ` jason at gcc dot gnu.org
2014-07-04 8:24 ` jakub at gcc dot gnu.org
2014-07-08 2:57 ` brooks at gcc dot gnu.org
2014-07-08 22:34 ` jason 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-61382-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: link
Be 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).