public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: bangerth@dealii.org
To: duchier@ps.uni-sb.de, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org,
	nobody@gcc.gnu.org
Subject: Re: optimization/8634: [3.2/3.3 regression] incorrect code for inlining of memcpy under -O2
Date: Wed, 04 Dec 2002 14:31:00 -0000	[thread overview]
Message-ID: <20021204223158.25767.qmail@sources.redhat.com> (raw)

Old Synopsis: incorrect inlining of memcpy under -O2
New Synopsis: [3.2/3.3 regression] incorrect code for inlining of memcpy under -O2

State-Changed-From-To: open->analyzed
State-Changed-By: bangerth
State-Changed-When: Wed Dec  4 14:31:57 2002
State-Changed-Why:
    Confirmed. This program
    ----------------------------
    #include <stdio.h>
    #include <string.h>
    
    int main()
    {
      char* buffer = new char[8];
      const char head[8] = {
        'A', 'B', 'C', 'D',
        'E', 'F', 'G', 'H'
      };
      memcpy(buffer,head,8);
      for(int i=0;i<8;i++)
        printf ("[%u] = %c, %c\n", i, head[i], buffer[i]);
      return 0;
    }
    --------------------------------
    yields with 3.2.2pre, 3.3pre, and 2.95 respectively:
    
    tmp/g> /home/bangerth/bin/gcc-3.2.2-pre/bin/c++ -O2 bug.cc  &&  ./a.out
    [0] = A, A
    [1] = B,
    [2] = C,
    [3] = D,
    [4] = E, E
    [5] = F, F
    [6] = G, G
    [7] = H, H
    
    
    tmp/g> /home/bangerth/bin/gcc-3.3-pre/bin/c++ -O2 bug.cc  &&  ./a.out
    [0] = A, A
    [1] = B,
    [2] = C,
    [3] = D,
    [4] = E, E
    [5] = F, F
    [6] = G, G
    [7] = H, H
    
    
    tmp/g> c++ -O2 bug.cc  &&  ./a.out
    [0] = A, A
    [1] = B, B
    [2] = C, C
    [3] = D, D
    [4] = E, E
    [5] = F, F
    [6] = G, G
    [7] = H, H
    
    
    That seems like a regression.

http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=8634


             reply	other threads:[~2002-12-04 22:31 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-04 14:31 bangerth [this message]
2002-12-10  0:26 Glen Nakamura
2002-12-23 16:36 Janis Johnson
2003-03-23 18:21 Glen Nakamura

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=20021204223158.25767.qmail@sources.redhat.com \
    --to=bangerth@dealii.org \
    --cc=duchier@ps.uni-sb.de \
    --cc=gcc-bugs@gcc.gnu.org \
    --cc=gcc-gnats@gcc.gnu.org \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=nobody@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).