From: Mike Frysinger <vapier@gentoo.org>
To: gdb-patches@sourceware.org
Subject: Re: [PATCH] gdb: workaround sparc memcpy fortify error
Date: Mon, 19 Apr 2010 18:59:00 -0000 [thread overview]
Message-ID: <201004191458.55123.vapier@gentoo.org> (raw)
In-Reply-To: <1269029490-6943-1-git-send-email-vapier@gentoo.org>
[-- Attachment #1: Type: Text/Plain, Size: 172 bytes --]
On Friday 19 March 2010 16:11:30 Mike Frysinger wrote:
> This is due to the gcc optimizer bug PR37060, so tweak the gdb_assert ()
> to avoid the issue.
is this OK ?
-mike
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2010-04-19 18:59 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-19 2:09 [PATCH] gdb: fix " Mike Frysinger
2010-03-19 7:45 ` Eli Zaretskii
2010-03-19 8:18 ` Hui Zhu
2010-03-19 8:42 ` Andreas Schwab
2010-03-19 17:10 ` Mike Frysinger
2010-03-19 9:26 ` Mark Kettenis
2010-03-19 17:09 ` Mike Frysinger
2010-03-19 20:11 ` [PATCH] gdb: workaround " Mike Frysinger
2010-04-19 18:59 ` Mike Frysinger [this message]
2010-04-21 15:30 ` Joel Brobecker
2010-04-21 15:38 ` Tom Tromey
2010-04-21 16:01 ` Joel Brobecker
2010-04-21 16:10 ` Mark Kettenis
2010-04-21 19:40 ` Mike Frysinger
2010-04-21 19:56 ` Mark Kettenis
2010-04-21 20:12 ` Mike Frysinger
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=201004191458.55123.vapier@gentoo.org \
--to=vapier@gentoo.org \
--cc=gdb-patches@sourceware.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