From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Ralf Corsepius <ralf.corsepius@rtems.org>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>,
Joel Sherrill <Joel.Sherrill@oarcorp.com>
Subject: Re: sparc-tdep.c: __builtin___memcpy_chk overflows destination buffer
Date: Thu, 17 Sep 2009 18:05:00 -0000 [thread overview]
Message-ID: <20090917180452.GA2163@host0.dyn.jankratochvil.net> (raw)
In-Reply-To: <4AB1A090.8030701@rtems.org>
Hi Ralf,
I think this is more a GCC fault:
[4.3/4.4/4.5 regression] Bogus __builtin___memcpy_chk overflow warning
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=37060
Regards,
Jan
next prev parent reply other threads:[~2009-09-17 18:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-17 2:36 Ralf Corsepius
2009-09-17 6:25 ` Mark Kettenis
2009-09-17 15:43 ` Joel Brobecker
2009-09-17 18:05 ` Jan Kratochvil [this message]
2009-09-18 5:01 ` Ralf Corsepius
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=20090917180452.GA2163@host0.dyn.jankratochvil.net \
--to=jan.kratochvil@redhat.com \
--cc=Joel.Sherrill@oarcorp.com \
--cc=gdb-patches@sourceware.org \
--cc=ralf.corsepius@rtems.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