public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Glen Nakamura <glen@imodulo.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: Sun, 23 Mar 2003 18:21:00 -0000	[thread overview]
Message-ID: <20030323181600.3283.qmail@sources.redhat.com> (raw)

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

From: Glen Nakamura <glen@imodulo.com>
To: gcc-gnats@gcc.gnu.org, gcc-bugs@gcc.gnu.org
Cc:  
Subject: Re: optimization/8634: [3.2/3.3 regression] incorrect code for inlining of memcpy under -O2
Date: Sun, 23 Mar 2003 18:07:39 +0000

 --wRRV7LY7NUeQGEoC
 Content-Type: text/plain; charset=us-ascii
 Content-Disposition: inline
 
 http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=8634
 
 Attached is an extended test case for constant initializers.
 
 
 --wRRV7LY7NUeQGEoC
 Content-Type: text/plain; charset=us-ascii
 Content-Disposition: attachment; filename="pr8634.c"
 
 /* PR optimization/8634 */
 /* Contributed by Glen Nakamura <glen@imodulo.com> */
 
 extern void abort (void);
 
 struct foo {
   char a, b, c, d, e, f, g, h, i, j;
 };
 
 int test1 ()
 {
   const char X[8] = { 'A', 'B', 'C', 'D', 'E', 'F', 'G', 'H' };
   char buffer[8];
   __builtin_memcpy (buffer, X, 8);
   if (buffer[0] != 'A' || buffer[1] != 'B'
       || buffer[2] != 'C' || buffer[3] != 'D'
       || buffer[4] != 'E' || buffer[5] != 'F'
       || buffer[6] != 'G' || buffer[7] != 'H')
     abort ();
   return 0;
 }
 
 int test2 ()
 {
   const char X[10] = { 'A', 'B', 'C', 'D', 'E' };
   char buffer[10];
   __builtin_memcpy (buffer, X, 10);
   if (buffer[0] != 'A' || buffer[1] != 'B'
       || buffer[2] != 'C' || buffer[3] != 'D'
       || buffer[4] != 'E' || buffer[5] != '\0'
       || buffer[6] != '\0' || buffer[7] != '\0'
       || buffer[8] != '\0' || buffer[9] != '\0')
     abort ();
   return 0;
 }
 
 int test3 ()
 {
   const struct foo X = { a : 'A', c : 'C', e : 'E', g : 'G', i : 'I' };
   char buffer[10];
   __builtin_memcpy (buffer, &X, 10);
   if (buffer[0] != 'A' || buffer[1] != '\0'
       || buffer[2] != 'C' || buffer[3] != '\0'
       || buffer[4] != 'E' || buffer[5] != '\0'
       || buffer[6] != 'G' || buffer[7] != '\0'
       || buffer[8] != 'I' || buffer[9] != '\0')
     abort ();
   return 0;
 }
 
 int test4 ()
 {
   const struct foo X = { .b = 'B', .d = 'D', .f = 'F', .h = 'H' , .j = 'J' };
   char buffer[10];
   __builtin_memcpy (buffer, &X, 10);
   if (buffer[0] != '\0' || buffer[1] != 'B'
       || buffer[2] != '\0' || buffer[3] != 'D'
       || buffer[4] != '\0' || buffer[5] != 'F'
       || buffer[6] != '\0' || buffer[7] != 'H'
       || buffer[8] != '\0' || buffer[9] != 'J')
     abort ();
   return 0;
 }
 
 int main ()
 {
   test1 (); test2 (); test3 (); test4 ();
   return 0;
 }
 
 --wRRV7LY7NUeQGEoC--


             reply	other threads:[~2003-03-23 18:16 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-23 18:21 Glen Nakamura [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-12-23 16:36 Janis Johnson
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=20030323181600.3283.qmail@sources.redhat.com \
    --to=glen@imodulo.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).