public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ville.voutilainen at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/61491] New: An explicit specialization of a member enumeration of a class template is rejected
Date: Thu, 12 Jun 2014 21:41:00 -0000	[thread overview]
Message-ID: <bug-61491-4@http.gcc.gnu.org/bugzilla/> (raw)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61491

            Bug ID: 61491
           Summary: An explicit specialization of a member enumeration of
                    a class template is rejected
           Product: gcc
           Version: 4.10.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c++
          Assignee: unassigned at gcc dot gnu.org
          Reporter: ville.voutilainen at gmail dot com

#include <iostream>

template <class D> struct Base 
{ 
    enum class E : unsigned; 
    E e; 
    Base(E e) : e(e) {} 
}; 

struct X; 

template<> enum class Base<X>::E : unsigned { a, b }; 

struct X : Base<X> 
{ 
    X() : Base<X>(E::b) {} 
};

int main()
{ 
    X x; 
    std::cout << static_cast<unsigned>(x.e) << std::endl;
}

[ville@localhost ~]$ g++ --std=c++11 -pedantic -o plash plash.cpp 
plash.cpp:12:52: warning: template specialization of ‘enum class Base<X>::E’
not allowed by ISO C++ [-Wpedantic]
 template<> enum class Base<X>::E : unsigned { a, b }; 
                                                    ^
Clang accepts the code.
>From gcc-bugs-return-454063-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jun 12 21:55:44 2014
Return-Path: <gcc-bugs-return-454063-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 23952 invoked by alias); 12 Jun 2014 21:55:44 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 23900 invoked by uid 48); 12 Jun 2014 21:55:41 -0000
From: "davejohansen at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/60731] [4.7/4.8/4.9 Regression] dynamic library not getting reinitialized on multiple calls to dlopen()
Date: Thu, 12 Jun 2014 21:55:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: davejohansen at gmail dot com
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: jason at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 4.7.4
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-60731-4-pNFigz1DbW@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-60731-4@http.gcc.gnu.org/bugzilla/>
References: <bug-60731-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2014-06/txt/msg01145.txt.bz2
Content-length: 269

https://gcc.gnu.org/bugzilla/show_bug.cgi?id`731

--- Comment #11 from Dave Johansen <davejohansen at gmail dot com> ---
Can this please be reopened? It was determined in the glibc bugzilla that this
is a gcc problem because of the incorrect setting of unique flag.


             reply	other threads:[~2014-06-12 21:41 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-12 21:41 ville.voutilainen at gmail dot com [this message]
2014-06-12 21:57 ` [Bug c++/61491] " ville.voutilainen at gmail dot com
2014-12-14 16:46 ` redi at gcc dot gnu.org
2015-07-09 15:14 ` 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-61491-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).