public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: Andrew Thomas Pinski <pinskia@gmail.com>
To: "gcc-bugzilla@gcc.gnu.org" <gcc-bugzilla@gcc.gnu.org>
Cc: "gcc-bugs@gcc.gnu.org" <gcc-bugs@gcc.gnu.org>
Subject: Re: [Bug target/39226]  New: [4.4 Regression] gcc_assert (verify_initial_elim_offsets ()); ICE
Date: Wed, 18 Feb 2009 10:30:00 -0000	[thread overview]
Message-ID: <BBE584F0-8566-416D-87A1-A751D7038DC0@gmail.com> (raw)
In-Reply-To: <bug-39226-87@http.gcc.gnu.org/bugzilla/>

This is mostly likely due to my no micro code patch. I see what causes  
it tommorow.

Sent from my iPhone

On Feb 17, 2009, at 11:55 PM, "jakub at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org 
 > wrote:

> /* { dg-do compile } */
> /* { dg-options "-O2" } */
> /* { dg-options "-O2 -mtune=cell -mminimal-toc" { target { powerpc*- 
> *-* && lp64
> } } } */
>
> struct A
> {
>  char *a;
>  unsigned int b : 1;
>  unsigned int c : 31;
> };
>
> struct B
> {
>  struct A *d;
> };
>
> void
> foo (struct B *x, unsigned long y)
> {
>  if (x->d[y].c)
>    return;
>  if (x->d[y].b)
>    x->d[y].a = 0;
> }
>
> ICEs with -m64 -O2 -mtune=cell -mminimal-toc, as elimination offsets  
> change.
>
>
> -- 
>           Summary: [4.4 Regression] gcc_assert  
> (verify_initial_elim_offsets
>                    ()); ICE
>           Product: gcc
>           Version: 4.4.0
>            Status: UNCONFIRMED
>          Keywords: ice-on-valid-code
>          Severity: normal
>          Priority: P3
>         Component: target
>        AssignedTo: unassigned at gcc dot gnu dot org
>        ReportedBy: jakub at gcc dot gnu dot org
> GCC target triplet: powerpc64-linux
>
>
> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39226
>


  parent reply	other threads:[~2009-02-18 10:30 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-18  7:55 jakub at gcc dot gnu dot org
2009-02-18  7:56 ` [Bug target/39226] " jakub at gcc dot gnu dot org
2009-02-18 10:30 ` Andrew Thomas Pinski [this message]
2009-02-18 10:30 ` pinskia at gmail dot com
2009-02-18 12:28 ` jakub at gcc dot gnu dot org
2009-02-18 19:35 ` pinskia at gcc dot gnu dot org
2009-02-18 19:41 ` jakub at gcc dot gnu dot org
2009-02-18 19:42 ` pinskia at gcc dot gnu dot org
2009-02-21 13:08 ` rguenth at gcc dot gnu dot org
2009-03-03 14:25 ` jakub at gcc dot gnu dot org
2009-04-01 16:19 ` [Bug target/39226] [4.4/4.5 " jakub at gcc dot gnu dot org
2009-04-01 16:22 ` jakub at gcc dot gnu dot org
2009-04-01 18:24 ` jakub at gcc dot gnu dot org
2009-04-01 18:25 ` jakub 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=BBE584F0-8566-416D-87A1-A751D7038DC0@gmail.com \
    --to=pinskia@gmail.com \
    --cc=gcc-bugs@gcc.gnu.org \
    --cc=gcc-bugzilla@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).