public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Janis Johnson <janis187@us.ibm.com>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: optimization/8634: [3.2/3.3 regression] incorrect code for inlining  of memcpy under -O2
Date: Mon, 23 Dec 2002 16:36:00 -0000	[thread overview]
Message-ID: <20021224003601.912.qmail@sources.redhat.com> (raw)

The following reply was made to PR optimization/8634; it has been noted by GNATS.

From: Janis Johnson <janis187@us.ibm.com>
To: gcc-gnats@gcc.gnu.org, gcc-prs@gcc.gnu.org, duchier@ps.uni-sb.de,
   gcc-bugs@gcc.gnu.org, nobody@gcc.gnu.org
Cc:  
Subject: Re: optimization/8634: [3.2/3.3 regression] incorrect code for inlining 
 of memcpy under -O2
Date: Mon, 23 Dec 2002 16:37:21 -0800

 The regression reported in PR optimization/8634 showed up
 starting with this patch (strange but true):
 
 Fri Dec 21 23:30:14 CET 2001  Jan Hubicka  <jh@suse.cz>
      * i386.h (TARGET_CPU_DEFAULT_pentium_mmx): New.
     (TARGET_CPU_DEFAULT_*): Renumber.
 
 I used this test case that Wolfgang provided.  It aborts
 when the wrong code is generated for -O2 on i686-linux:
 
 --------------
 /* incorrect code for inlining of memcpy under -O2 */
 
 #include <string.h>
 #include <stdlib.h>
 
 int
 main ()
 {
   int i;
   char buffer[8];
   const char head[8] =
     { 'A', 'B', 'C', 'D', 'E', 'F', 'G', 'H' };
   memcpy (buffer, head, 8);
   for (i = 0; i < 8; i++)
     if (head[i] != buffer[i])
       abort ();
   return 0;
 }
 --------------
 
 http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=8634
 
 
 


             reply	other threads:[~2002-12-24  0:36 UTC|newest]

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

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=20021224003601.912.qmail@sources.redhat.com \
    --to=janis187@us.ibm.com \
    --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).