public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "js at lastlog dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/51927] [C++0x] Cannot access non-static members in initializer
Date: Wed, 05 Dec 2012 17:29:00 -0000	[thread overview]
Message-ID: <bug-51927-4-Y8mhBIO7YU@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-51927-4@http.gcc.gnu.org/bugzilla/>


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51927

js at lastlog dot de changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |js at lastlog dot de

--- Comment #4 from js at lastlog dot de 2012-12-05 17:29:35 UTC ---
still seems to be broken in 4.7.2 :-P

but is known to be working with llvm 3.2

# make
simple.cpp: In lambda function:
simple.cpp:11:5: error: invalid use of non-static data member ‘testee::l1’
simple.cpp:15:9: error: from this location
make[2]: *** [CMakeFiles/simple.dir/simple.cpp.o] Error 1
make[1]: *** [CMakeFiles/simple.dir/all] Error 2
make: *** [all] Error 2
*** Failed ***

# g++ --version
g++ (Ubuntu/Linaro 4.7.2-11precise2) 4.7.2
Copyright (C) 2012 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.


  parent reply	other threads:[~2012-12-05 17:29 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-21  3:12 [Bug c++/51927] New: " gccearlyadopter@trash-mail.com
2012-05-30  7:58 ` [Bug c++/51927] " gccearlyadopter@trash-mail.com
2012-05-30  8:52 ` redi at gcc dot gnu.org
2012-05-30 12:43 ` gccearlyadopter@trash-mail.com
2012-12-05 17:29 ` js at lastlog dot de [this message]
2013-05-04 12:20 ` paolo.carlini at oracle dot com
2013-05-04 12:33 ` paolo.carlini at oracle dot com

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-51927-4-Y8mhBIO7YU@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).