From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-bugs-return-407725-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Received: (qmail 25431 invoked by alias); 26 Nov 2012 12:12:32 -0000
Received: (qmail 25359 invoked by uid 48); 26 Nov 2012 12:12:13 -0000
From: "paolo.carlini at oracle dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/51242] [C++11] Unable to use strongly typed enums as bit fields
Date: Mon, 26 Nov 2012 12:12: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-Keywords: rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: paolo.carlini at oracle dot com
X-Bugzilla-Status: NEW
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Changed-Fields: CC
Message-ID: <bug-51242-4-e16OtXsFWa@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-51242-4@http.gcc.gnu.org/bugzilla/>
References: <bug-51242-4@http.gcc.gnu.org/bugzilla/>
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
Content-Type: text/plain; charset="UTF-8"
MIME-Version: 1.0
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
X-SW-Source: 2012-11/txt/msg02387.txt.bz2


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

Paolo Carlini <paolo.carlini at oracle dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |paolo.carlini at oracle dot
                   |                            |com

--- Comment #15 from Paolo Carlini <paolo.carlini at oracle dot com> 2012-11-26 12:12:12 UTC ---
To be clear, for:

enum class Code {
  SUCCESS = 0
};

Code a;// = static_cast<Code>(SHRT_MAX+1);

short r[] = {a};

we *error* out anyway, isn't that we are only emitting a warning and only when
we are assigning the SHRT_MAX + 1.