public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "reichelt at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/35744]  New: [4.1/4.2/4.3/4.4 regression] ICE attributes for invalid types
Date: Fri, 28 Mar 2008 21:42:00 -0000	[thread overview]
Message-ID: <bug-35744-1771@http.gcc.gnu.org/bugzilla/> (raw)

The following invalid code snippets triggers an ICE since GCC 4.1.0:

=========================================
struct A
{
  void x[1] __attribute__((packed));
};
=========================================

bug.c:3: error: declaration of 'x' as array of voids
bug.c:3: internal compiler error: tree check: expected class 'type', have
'exceptional' (error_mark) in handle_packed_attribute, at c-common.c:4653
Please submit a full bug report, [etc.]


Also other attributes applied to invalid variables cause ICEs
in various places, e.g.

=================================================
typedef char x[N] __attribute__((aligned(4)));
=================================================

bug.c:1: error: 'N' undeclared here (not in a function)
bug.c:1: internal compiler error: tree check: expected class 'type', have
'exceptional' (error_mark) in build_variant_type_copy, at tree.c:4180
Please submit a full bug report, [etc.]

=================================================
void x[1] __attribute__((vector_size(8)));
=================================================

bug.c:1: error: declaration of 'x' as array of voids
bug.c:1: internal compiler error: tree check: expected class 'type', have
'exceptional' (error_mark) in handle_vector_size_attribute, at c-common.c:6070
Please submit a full bug report, [etc.]

=================================================
void x[1] __attribute__((may_alias));
=================================================

bug.c:1: error: declaration of 'x' as array of voids
bug.c:1: internal compiler error: tree check: expected class 'type', have
'exceptional' (error_mark) in decl_attributes, at attribs.c:355
Please submit a full bug report, [etc.]


-- 
           Summary: [4.1/4.2/4.3/4.4 regression] ICE attributes for invalid
                    types
           Product: gcc
           Version: 4.4.0
            Status: UNCONFIRMED
          Keywords: ice-on-invalid-code, error-recovery, monitored
          Severity: normal
          Priority: P3
         Component: c
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: reichelt at gcc dot gnu dot org


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


             reply	other threads:[~2008-03-28 21:42 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-28 21:42 reichelt at gcc dot gnu dot org [this message]
2008-03-28 21:46 ` [Bug c/35744] " reichelt at gcc dot gnu dot org
2008-04-11  6:57 ` reichelt at gcc dot gnu dot org
2008-04-12  9:24 ` [Bug c/35744] [4.1/4.2/4.3 " reichelt at gcc dot gnu dot org
2008-04-15  9:33 ` jakub at gcc dot gnu dot org
2008-04-17 19:36 ` reichelt at gcc dot gnu dot org
2008-04-17 19:43 ` reichelt at gcc dot gnu dot org
2008-04-17 19:49 ` [Bug c/35744] [4.1 " reichelt at gcc dot gnu dot org
2008-07-04 16:19 ` jsm28 at gcc dot gnu dot 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-35744-1771@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).