From: Nathan Froyd <froydnj@codesourcery.com>
To: Tom Tromey <tromey@redhat.com>
Cc: Doug Evans <dje@google.com>, Pedro Alves <pedro@codesourcery.com>,
gdb@sourceware.org
Subject: Re: store.exp failure on i686-linux with newer gcc's
Date: Fri, 04 Sep 2009 20:17:00 -0000 [thread overview]
Message-ID: <20090904201734.GY29075@codesourcery.com> (raw)
In-Reply-To: <m3ab1ablnk.fsf@fleche.redhat.com>
On Fri, Sep 04, 2009 at 12:38:23PM -0600, Tom Tromey wrote:
> I see now that read_pieced_value will only be called to fill in a lazy
> value. So, you are correct, this can't happen for values on the
> history.
>
> This patch is ok.
Thanks, committed.
-Nathan
next prev parent reply other threads:[~2009-09-04 20:17 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-03 21:50 Doug Evans
2009-09-03 21:58 ` Joel Brobecker
2009-09-03 22:04 ` Pedro Alves
2009-09-03 22:17 ` Doug Evans
2009-09-03 23:44 ` Nathan Froyd
2009-09-04 16:05 ` Tom Tromey
2009-09-04 17:49 ` Nathan Froyd
2009-09-04 18:38 ` Tom Tromey
2009-09-04 20:17 ` Nathan Froyd [this message]
2009-09-04 20:18 ` Doug Evans
2009-09-04 21:23 ` Tom Tromey
2009-09-04 21:28 ` Daniel Jacobowitz
2009-09-04 22:28 ` Tom Tromey
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=20090904201734.GY29075@codesourcery.com \
--to=froydnj@codesourcery.com \
--cc=dje@google.com \
--cc=gdb@sourceware.org \
--cc=pedro@codesourcery.com \
--cc=tromey@redhat.com \
/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