public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Martin Kahlert <martin.kahlert@infineon.com>
To: gcc-gnats@gcc.gnu.org
Subject: c/7010: Bug in 3.1 with inline memcpy
Date: Thu, 13 Jun 2002 01:16:00 -0000 [thread overview]
Message-ID: <200206130806.g5D86gL26548@keksy.muc.infineon.com> (raw)
>Number: 7010
>Category: c
>Synopsis: Bug in 3.1 with inline memcpy
>Confidential: no
>Severity: serious
>Priority: medium
>Responsible: unassigned
>State: open
>Class: wrong-code
>Submitter-Id: net
>Arrival-Date: Thu Jun 13 01:16:00 PDT 2002
>Closed-Date:
>Last-Modified:
>Originator: Martin Kahlert
>Release: 3.1.1 20020610 (prerelease)
>Organization:
Infineon AG
>Environment:
System: Linux keksy 2.4.18 #9 SMP Thu Mar 14 17:35:28 MET 2002 i686 unknown
Architecture: i686
host: i686-pc-linux-gnu
build: i686-pc-linux-gnu
target: i686-pc-linux-gnu
configured with: ../gcc-20020610/configure --prefix=/sw/snapshots --enable-languages=f77,c++,java --disable-threads --enable-shared=libstdc++
>Description:
-minline-all-stringops has a problem with memcpy (SegFault).
>How-To-Repeat:
# cat bug.c
#include <string.h>
int main()
{
char dst[16];
char src[16];
int tocopy = 5;
memcpy (dst+5, src, tocopy);
return 0;
}
$ gcc -O -minline-all-stringops -o bug bug.c
$ ./bug
>Fix:
Omit -minline-all-stringops from command line.
>Release-Note:
>Audit-Trail:
>Unformatted:
next reply other threads:[~2002-06-13 8:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-13 1:16 Martin Kahlert [this message]
2002-06-13 9:06 Jan Hubicka
2002-06-13 9:16 Jakub Jelinek
2002-06-13 9:26 Richard Henderson
2002-06-20 14:10 gerald
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=200206130806.g5D86gL26548@keksy.muc.infineon.com \
--to=martin.kahlert@infineon.com \
--cc=gcc-gnats@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).