public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/27409] ICE in get_constraint_for_component_ref
Date: Wed, 03 May 2006 16:05:00 -0000	[thread overview]
Message-ID: <20060503160516.17208.qmail@sourceware.org> (raw)
In-Reply-To: <bug-27409-183@http.gcc.gnu.org/bugzilla/>



------- Comment #1 from rguenth at gcc dot gnu dot org  2006-05-03 16:05 -------
Confirmed.  We access a zero-sized part of the structure:

    arg 1 <field_decl 0x2a959f2180 f type <record_type 0x2a959dfb00 thang_t>
        BLK file t.c line 16 size <integer_cst 0x2a958ab750 0> unit size
<integer_cst 0x2a95891720 0>
        align 8 offset_align 128
        offset <integer_cst 0x2a958ab0f0 constant invariant 16>
        bit offset <integer_cst 0x2a95891bd0 constant invariant 32> context
<record_type 0x2a959dfe70>
        chain <field_decl 0x2a959f2240 g type <record_type 0x2a959dfdc0
thing_t>
            BLK file t.c line 17
            size <integer_cst 0x2a958ab0c0 constant invariant 128> unit size
<integer_cst 0x2a958ab0f0 16>
            align 64 offset_align 128 offset <integer_cst 0x2a958ab0f0 16>
            bit offset <integer_cst 0x2a95891d80 constant invariant 64> context
<record_type 0x2a959dfe70>>>>

The following testcase also ICEs on 32bit targets:

typedef struct {
        struct { } z;
} thang_t;
struct {
        short           e;
        thang_t         f;
        int g;
} my_struct;
void function(int blaz)
{ thang_t *fp = &my_struct.f; foo(fp);}

the important thing is that there has to be padding after e and the zero-sized
f.


-- 

rguenth at gcc dot gnu dot org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEW
     Ever Confirmed|0                           |1
   Last reconfirmed|0000-00-00 00:00:00         |2006-05-03 16:05:15
               date|                            |


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


  reply	other threads:[~2006-05-03 16:05 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-03 15:46 [Bug middle-end/27409] New: " matz at suse dot de
2006-05-03 16:05 ` rguenth at gcc dot gnu dot org [this message]
2006-05-03 16:06 ` [Bug middle-end/27409] " rguenth at gcc dot gnu dot org
2006-05-03 16:12 ` [Bug middle-end/27409] [4.1/4.2 Regression] " rguenth at gcc dot gnu dot org
2006-05-03 16:13 ` rguenth at gcc dot gnu dot org
2006-05-03 17:53 ` matz at suse dot de
2006-05-03 17:54 ` matz at suse dot de
2006-05-07 21:04 ` rguenth at gcc dot gnu dot org
2006-05-08  6:53 ` [Bug middle-end/27409] [4.1 " pinskia at gcc dot gnu dot org
2006-05-09 14:33 ` rguenth at gcc dot gnu dot org
2006-05-09 14:33 ` rguenth at gcc dot gnu dot org
2006-05-15 19:32 ` patchapp at dberlin 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=20060503160516.17208.qmail@sourceware.org \
    --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).