Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Tom Tromey <tromey@redhat.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [patch] Code cleanup: Introduce allocate_optimized_out_value
Date: Tue, 12 Jul 2011 21:17:00 -0000	[thread overview]
Message-ID: <m38vs3fbo5.fsf@fleche.redhat.com> (raw)
In-Reply-To: <20110712204311.GA324@host1.jankratochvil.net> (Jan Kratochvil's	message of "Tue, 12 Jul 2011 22:43:11 +0200")

>>>>> "Jan" == Jan Kratochvil <jan.kratochvil@redhat.com> writes:

Jan> this is a code cleanup.  Additionally it makes more optimized_out values lazy.
Jan> IIRC I had some compatibility problems before with it but I no longer see any
Jan> regressions, maybe since:
Jan> 	[patch 1/2] Make values more lazy if possible
Jan> 	http://sourceware.org/ml/gdb-patches/2011-01/msg00123.html
Jan> or thanks to some other patch.

It looks ok to me.

Tom


  reply	other threads:[~2011-07-12 21:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-12 21:09 Jan Kratochvil
2011-07-12 21:17 ` Tom Tromey [this message]
2011-07-12 21:37   ` Jan Kratochvil

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=m38vs3fbo5.fsf@fleche.redhat.com \
    --to=tromey@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=jan.kratochvil@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