public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/27285]  New: [4.1 regression] ivopts postgresql miscompilation
Date: Mon, 24 Apr 2006 15:33:00 -0000	[thread overview]
Message-ID: <bug-27285-87@http.gcc.gnu.org/bugzilla/> (raw)

extern void abort (void);

struct S { unsigned char a, b, c, d[16]; };

void __attribute__ ((noinline))
foo (struct S *x, struct S *y)
{
  int a, b;
  unsigned char c, *d, *e;

  b = x->b;
  d = x->d;
  e = y->d;
  a = 0;
  while (b)
    {
      if (b >= 8)
        {
          c = 0xff;
          b -= 8;
        }
      else
        {
          c = 0xff << (8 - b);
          b = 0;
        }

      e[a] = d[a] & c;
      a++;
    }
}

int
main (void)
{
  struct S x = { 0, 25, 0, { 0xaa, 0xbb, 0xcc, 0xdd }};
  struct S y = { 0, 0, 0, { 0 }};

  foo (&x, &y);
  if (x.d[0] != y.d[0] || x.d[1] != y.d[1]
      || x.d[2] != y.d[2] || (x.d[3] & 0x80) != y.d[3])
    abort ();
   return 0;
}

On i686-linux with -O2 -m32 the loop is miscompiled, it copies over just
first 24 bits and not the 25th bit.  From quick skimming of the tree dumps,
this looks messed up by ivopts pass.  Seems to be a recent regression,
at least 20060304 GCC 4.1.x worked fine, while 20060420 does not.


-- 
           Summary: [4.1 regression] ivopts postgresql miscompilation
           Product: gcc
           Version: 4.1.1
            Status: UNCONFIRMED
          Severity: critical
          Priority: P3
         Component: tree-optimization
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: jakub at gcc dot gnu dot org
GCC target triplet: i686-linux


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


             reply	other threads:[~2006-04-24 15:33 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-24 15:33 jakub at gcc dot gnu dot org [this message]
2006-04-24 15:50 ` [Bug tree-optimization/27285] " jakub at gcc dot gnu dot org
2006-04-24 16:18 ` pinskia at gcc dot gnu dot org
2006-04-24 21:40 ` pinskia at gcc dot gnu dot org
2006-04-24 21:41 ` pinskia at gcc dot gnu dot org
2006-04-25  7:37 ` jakub at gcc dot gnu dot org
2006-05-04  6:40 ` jakub at gcc dot gnu dot org
2006-05-04  6:44 ` jakub at gcc dot gnu dot org
2006-05-08 15:30 ` roger at eyesopen dot com

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-27285-87@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).