From: Daniel Jacobowitz <drow@false.org>
To: Vladimir Prus <ghost@cs.msu.su>
Cc: gdb-patches@sources.redhat.com
Subject: Re: Robustify mi-var-cp
Date: Tue, 09 Jan 2007 21:50:00 -0000 [thread overview]
Message-ID: <20070109215048.GG30631@nevyn.them.org> (raw)
In-Reply-To: <200701092355.21537.ghost@cs.msu.su>
On Tue, Jan 09, 2007 at 11:55:21PM +0300, Vladimir Prus wrote:
>
> This test fails for me, apparently due to compiler version dependency.
> The attached patch makes sure we don't try to access variables
> that are out of scope. OK?
OK (with a changelog entry)
> + /* Dummy assignment to keep 'x' in scope. */
(and a second space after the dot, for old time's sake)
--
Daniel Jacobowitz
CodeSourcery
prev parent reply other threads:[~2007-01-09 21:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-09 20:58 Vladimir Prus
2007-01-09 21:50 ` Daniel Jacobowitz [this message]
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=20070109215048.GG30631@nevyn.them.org \
--to=drow@false.org \
--cc=gdb-patches@sources.redhat.com \
--cc=ghost@cs.msu.su \
/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