public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "daniel.kruegler at googlemail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/51373] [C++0x] ICE for static pointer to member initialized in-class
Date: Sat, 03 Dec 2011 19:18:00 -0000	[thread overview]
Message-ID: <bug-51373-4-o3laZdxCJz@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-51373-4@http.gcc.gnu.org/bugzilla/>

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

Daniel Krügler <daniel.kruegler at googlemail dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |daniel.kruegler at
                   |                            |googlemail dot com

--- Comment #1 from Daniel Krügler <daniel.kruegler at googlemail dot com> 2011-12-03 19:17:09 UTC ---
(In reply to comment #0)
> gcc version 4.7.0 20111112 (experimental) (GCC) 

Also in 4.7.0 20111126 (experimental)

> Two seemingly relate ICEs when dealing with pointer to member:
> 
> struct foo {
>     int a = 42;
>     static int foo::*b = &foo::a;
> };

b needs to have a constexpr specifier here, but it ICEs also with that one
added. Even with the constexpr specifier that declaration should be ill-formed,
because the class definition must be complete for an in-class static data
member initializer. Also, the initializer for a is not needed to reproduce the
error.

> struct foo {
>     int a = 42;
>     static int foo::*b;
>     auto& c = b;
> };
> internal compiler error: in unify_one_argument, at cp/pt.c:15008

The declaration of c cannot use auto (only static data members may do) and the
ICE does no longer occur after the fix. In addition, the declaration of a is
not needed to reproduce the problem.


  parent reply	other threads:[~2011-12-03 19:18 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-01  4:36 [Bug c++/51373] New: " pubby.8 at gmail dot com
2011-12-01  9:19 ` [Bug c++/51373] [C++0x] " paolo.carlini at oracle dot com
2011-12-03 19:18 ` daniel.kruegler at googlemail dot com [this message]
2011-12-03 19:34 ` daniel.kruegler at googlemail dot com
2014-06-06 11:25 ` vl.still at gmail dot com
2014-06-06 12:14 ` vl.still at gmail 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-51373-4-o3laZdxCJz@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).