public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Jakub Jelinek <jakub@redhat.com>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: c/7010: Bug in 3.1 with inline memcpy
Date: Thu, 13 Jun 2002 09:16:00 -0000	[thread overview]
Message-ID: <20020613161602.1621.qmail@sources.redhat.com> (raw)

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

From: Jakub Jelinek <jakub@redhat.com>
To: Jan Hubicka <jh@suse.cz>
Cc: Martin Kahlert <martin.kahlert@infineon.com>, gcc-patches@gcc.gnu.org,
   rth@cygnus.com, aj@suse.de, gcc-gnats@gcc.gnu.org
Subject: Re: c/7010: Bug in 3.1 with inline memcpy
Date: Thu, 13 Jun 2002 12:13:12 -0400

 On Thu, Jun 13, 2002 at 06:05:55PM +0200, Jan Hubicka wrote:
 > > #include <string.h>
 > > 
 > > int main()
 > > {
 > >  char dst[16];
 > >  char src[16];
 > >  int tocopy = 5;
 > > 
 > >  memcpy (dst+5, src, tocopy);
 > > 
 > >  return 0;
 > > }
 > 
 > Oh no, another pasto in my code :(
 > I am just proffreading both functions to catch similar bugs, if they
 > exists.
 > 
 > Bootstrapped/regtested branch, OK for mainline/branch?
 > Ok to add testcase into mainline testsuite?
 
 I think the testcase would be useful on branch too, just
 it shouldn't use string.h but whatever simplified code reproduces this
 (as with string.h it depends on what exact libc you're using etc.).
 
 	Jakub


             reply	other threads:[~2002-06-13 16:16 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-13  9:16 Jakub Jelinek [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-06-20 14:10 gerald
2002-06-13  9:26 Richard Henderson
2002-06-13  9:06 Jan Hubicka
2002-06-13  1:16 Martin Kahlert

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=20020613161602.1621.qmail@sources.redhat.com \
    --to=jakub@redhat.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).