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++/60209] Declaration of user-defined literal operator cause error
Date: Sun, 16 Feb 2014 17:30:00 -0000	[thread overview]
Message-ID: <bug-60209-4-T3tcuuH9d6@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-60209-4@http.gcc.gnu.org/bugzilla/>

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

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

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |daniel.kruegler@googlemail.
                   |                            |com

--- Comment #1 from Daniel Krügler <daniel.kruegler at googlemail dot com> ---
My understanding is that CWG 1473 clarified this:

http://www.open-std.org/jtc1/sc22/wg21/docs/cwg_defects.html#1473
>From gcc-bugs-return-443839-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Feb 16 17:36:21 2014
Return-Path: <gcc-bugs-return-443839-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 5143 invoked by alias); 16 Feb 2014 17:36:20 -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 5116 invoked by uid 48); 16 Feb 2014 17:36:17 -0000
From: "reichelt at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/60226] New: ICE initializing array of elements with too large alignment
Date: Sun, 16 Feb 2014 17:36:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 4.9.0
X-Bugzilla-Keywords: error-recovery, ice-on-invalid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: reichelt at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status keywords bug_severity priority component assigned_to reporter
Message-ID: <bug-60226-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-02/txt/msg01596.txt.bz2
Content-length: 1795

http://gcc.gnu.org/bugzilla/show_bug.cgi?id`226

            Bug ID: 60226
           Summary: ICE initializing array of elements with too large
                    alignment
           Product: gcc
           Version: 4.9.0
            Status: UNCONFIRMED
          Keywords: error-recovery, ice-on-invalid-code
          Severity: normal
          Priority: P3
         Component: c
          Assignee: unassigned at gcc dot gnu.org
          Reporter: reichelt at gcc dot gnu.org

The following invalid code snippet triggers an ICE since GCC 4.0.0:

======================================================typedef int __attribute__ ((aligned(1 << 28))) int28;
int28 foo[4] = {};
======================================================
bug.c:2:1: error: alignment of array elements is greater than element size
 int28 foo[4] = {};
 ^
bug.c:2:1: internal compiler error: in round_up_loc, at fold-const.c:16882
0x7e8116 round_up_loc(unsigned int, tree_node*, int)
        ../../gcc/gcc/fold-const.c:16882
0x9e45bd finalize_type_size
        ../../gcc/gcc/stor-layout.c:1691
0x9e6936 layout_type(tree_node*)
        ../../gcc/gcc/stor-layout.c:2312
0xc0e1a2 build_array_type_1
        ../../gcc/gcc/tree.c:7840
0x5961e0 grokdeclarator
        ../../gcc/gcc/c/c-decl.c:5603
0x598c6d start_decl(c_declarator*, c_declspecs*, bool, tree_node*)
        ../../gcc/gcc/c/c-decl.c:4069
0x5e88ff c_parser_declaration_or_fndef
        ../../gcc/gcc/c/c-parser.c:1754
0x5eca5f c_parser_external_declaration
        ../../gcc/gcc/c/c-parser.c:1399
0x5ed359 c_parser_translation_unit
        ../../gcc/gcc/c/c-parser.c:1286
0x5ed359 c_parse_file()
        ../../gcc/gcc/c/c-parser.c:14026
0x63bc53 c_common_parse_file()
        ../../gcc/gcc/c-family/c-opts.c:1060
Please submit a full bug report, [etc.]


  reply	other threads:[~2014-02-16 17:30 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-15  4:29 [Bug c++/60209] New: " kariya_mitsuru at hotmail dot com
2014-02-16 17:30 ` daniel.kruegler at googlemail dot com [this message]
2014-05-11 14:44 ` [Bug c++/60209] " paolo.carlini at oracle dot com
2014-05-12 13:52 ` emsr at gcc dot gnu.org
2014-05-12 13:54 ` emsr at gcc dot gnu.org
2014-07-13 13:37 ` emsr at gcc dot gnu.org
2014-07-13 13:40 ` emsr 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-60209-4-T3tcuuH9d6@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).