public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ian at airs dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/55305] New: invalid aggregate constprop
Date: Tue, 13 Nov 2012 01:09:00 -0000	[thread overview]
Message-ID: <bug-55305-4@http.gcc.gnu.org/bugzilla/> (raw)


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

             Bug #: 55305
           Summary: invalid aggregate constprop
    Classification: Unclassified
           Product: gcc
           Version: 4.8.0
            Status: UNCONFIRMED
          Keywords: wrong-code
          Severity: blocker
          Priority: P3
         Component: tree-optimization
        AssignedTo: unassigned@gcc.gnu.org
        ReportedBy: ian@airs.com


When I compile and run this program with current mainline with -O0, -O1, or
-Og, it passes.  When I use -O2, it crashes.

This is a reduced version of a failure in the libgo testsuite.

extern void exit (int) __attribute__ ((noreturn));
extern void abort (void) __attribute__ ((noreturn));

struct t
{
  char dummy;
};

struct m
{
  const struct t *t;
  void (*m)(void);
};

struct s
{
  const struct m *m;
  void *o;
};

struct e
{
  const struct t *t;
  void *o;
};

struct ret
{
  struct s s;
  _Bool b;
};

const struct t t1 = { 1 };
const struct t t2 = { 2 };
const struct t t3 = { 3 };
const struct t t4 = { 4 };
const struct t t5 = { 5 };

void
pass (void)
{
  exit (0);
}

void
fail (void)
{
  abort ();
}

const struct m m1 = { &t4, fail };
const struct m m2 = { &t5, pass };

static struct e f2 (struct s s2, void *p);
static struct e f3 (struct s, void *) __attribute__ ((noinline));
static void f4 (struct s, void *) __attribute__ ((noinline));

struct ret c (struct s, const struct t *) __attribute__ ((noinline));

struct ret
c (struct s s1, const struct t *t)
{
  struct ret r;

  if (s1.m->t == t)
    {
      r.s.m = &m2;
      r.s.o = s1.o;
      r.b = 1;
    }
  else
    {
      r.s.m = 0;
      r.s.o = 0;
      r.b = 0;
    }
  return r;
}

void *m (void) __attribute__ ((noinline));

void *
m (void)
{
  return 0;
}

struct e
f1 (struct s s1, void *p)
{
  struct ret r;
  void *a;
  struct s a2;

  r = c (s1, &t5);
  if (r.b)
    return f2 (r.s, p);
  a = m ();
  a2.m = &m1;
  a2.o = a;
  return f2 (a2, p);
}

static struct e
f2 (struct s s2, void *p)
{
  struct e e1;

  e1 = f3 (s2, p);
  if (e1.t == &t2 && e1.o == 0)
    {
      e1.t = 0;
      e1.o = 0;
    }
  return e1;
}

static struct e
f3 (struct s s1, void *p)
{
  struct e r;

  f4 (s1, p);
  r.t = &t3;
  r.o = 0;
  return r;
}

struct s g1;
void *g2;

static void
f4 (struct s s1, void *p)
{
  g1 = s1;
  g2 = p;
  s1.m->m ();
}

int
main ()
{
  struct s s1;

  s1.m = &m2;
  s1.o = 0;
  f1 (s1, 0);
  abort ();
}


             reply	other threads:[~2012-11-13  1:09 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-13  1:09 ian at airs dot com [this message]
2012-11-13  1:13 ` [Bug tree-optimization/55305] " ian at airs dot com
2012-11-13 14:27 ` jamborm at gcc dot gnu.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-55305-4@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).