public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: alex.zatsman@analog.com
To: gcc-gnats@gcc.gnu.org, debian-gcc@lists.debian.org
Subject: c/7873: arm-linux-gcc fails when assigning address to a bit field
Date: Mon, 09 Sep 2002 15:26:00 -0000	[thread overview]
Message-ID: <E17oWpy-0007Jl-00@tula.spd.analog.com> (raw)


>Number:         7873
>Category:       c
>Synopsis:       arm-linux-gcc fails when assigning address to a bit field
>Confidential:   no
>Severity:       critical
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          ice-on-legal-code
>Submitter-Id:   net
>Arrival-Date:   Mon Sep 09 15:26:00 PDT 2002
>Closed-Date:
>Last-Modified:
>Originator:     Alex Zatsman
>Release:        arm-linux-gcc v.3.2
>Organization:
Analog Devices
>Environment:
System: Linux tula 2.4.9 #1 SMP Fri Oct 26 14:37:41 EDT 2001 i686 unknown
Architecture: i686

	
host: i386-pc-linux-gnu
build: i386-pc-linux-gnu
target: i386-pc-linux-gnu
configured with: arm-linux set 
>Description:

./arm-linux-gcc -c xxx2.c
xxx2.c: In function `foo':
xxx2.c:13: unrecognizable insn:
(insn 13 11 15 (set (reg:SI 34)
        (ashift:SI (symbol_ref:SI ("x0"))
            (const_int 12 [0xc]))) -1 (nil)
    (nil))
xxx2.c:13: Internal compiler error in extract_insn, at recog.c:2148
Please submit a full bug report,
with preprocessed source if appropriate.
See <URL:http://www.gnu.org/software/gcc/bugs.html> for instructions.

>How-To-Repeat:

/** Run "arm-linux-gcc -c" on this preprocessed segment : **/


unsigned int  x0  = 0;

typedef struct {
  unsigned int  field1 : 20;
  unsigned int  field2 : 12;
} XX;

static XX yy;

static void foo (void)
{
  yy.field1 = (unsigned int ) (&x0);
}





>Fix:
	You tell me :)
>Release-Note:
>Audit-Trail:
>Unformatted:


             reply	other threads:[~2002-09-09 22:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-09 15:26 alex.zatsman [this message]
2002-09-10  2:56 Richard Earnshaw
2002-09-10  8:47 rearnsha

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=E17oWpy-0007Jl-00@tula.spd.analog.com \
    --to=alex.zatsman@analog.com \
    --cc=debian-gcc@lists.debian.org \
    --cc=gcc-gnats@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).