public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/26087]  New: [4.2 Regression] ICE in df_find_use
Date: Fri, 03 Feb 2006 03:44:00 -0000	[thread overview]
Message-ID: <bug-26087-6528@http.gcc.gnu.org/bugzilla/> (raw)

I was going to do a --enable-checking=release buil to test some compile time
preformance but I ran into an ICE.  This does not happen on a
----enable-checking=yes build because the source is different
but the testcase is reproduce there.

The last time the reduced testcase (and full source, ifcvt.c) is known to work
is rev 110452.
I am testing with rev 110522.

Any trying to reduce this further causes the ICE to go away as the order of the
BBs have change but that seem wrong in general.   This is a real blocker as it
means when we branch the bootstrap starts to fail.

Reduced testcase:
extern void fancy_abort (void) __attribute__ ((__noreturn__));
typedef struct edge_def {
  int dest;
  int flags;
}*edge;
typedef struct {
  int **container;
}edge_iterator;
static __inline__ unsigned char ei_cond (edge_iterator ei3, edge *p)
{
  if (!ei_end_p (ei3))
    return 1;
  *p = 0;
  return 0;
}
int block_fallthru (edge_iterator ei1, edge e)
{
  while (ei_cond ((ei1), &(e)))
    {
      if (e->flags & 1)
        break;
      edge_iterator ei2 = ei1;
      if (!(ei2.container))
        fancy_abort ();
    }
  return (e) ? e->dest : 0;
}


-- 
           Summary: [4.2 Regression] ICE in df_find_use
           Product: gcc
           Version: 4.2.0
            Status: UNCONFIRMED
          Keywords: ice-on-valid-code, build
          Severity: blocker
          Priority: P3
         Component: rtl-optimization
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: pinskia at gcc dot gnu dot org
GCC target triplet: powerpc-darwin


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


             reply	other threads:[~2006-02-03  3:44 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-03  3:44 pinskia at gcc dot gnu dot org [this message]
2006-02-03  3:44 ` [Bug rtl-optimization/26087] " pinskia at gcc dot gnu dot org
2006-02-03  3:48 ` pinskia at gcc dot gnu dot org
2006-02-03 13:57 ` rakdver at gcc dot gnu dot org
2006-02-03 14:14 ` rakdver at gcc dot gnu dot org
2006-02-03 19:14 ` pinskia at gcc dot gnu dot org
2006-02-04 21:30 ` rakdver at gcc dot gnu dot org
2006-02-05 14:58 ` rakdver at gcc dot gnu dot org
2006-02-05 15:29 ` rakdver 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-26087-6528@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).