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] Fix implicit pointer vs. typedefs
Date: Mon, 18 Jul 2011 16:52:00 -0000	[thread overview]
Message-ID: <m3vcuz7gea.fsf@fleche.redhat.com> (raw)
In-Reply-To: <20110718150124.GA24706@host1.jankratochvil.net> (Jan	Kratochvil's message of "Mon, 18 Jul 2011 17:01:24 +0200")

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

Jan> found missing check_typedef in indirect_pieced_value, with the extended
Jan> testcase the fix will:
[...]
Jan> No regressions on {x86_64,x86_64-m32,i686}-fedora16pre-linux-gnu.
Jan> I will check it in if no responses appear.

Thanks Jan.  It looks good to me.

I have come around to your view that we should get rid of check_typedef.

Tom


  reply	other threads:[~2011-07-18 15:33 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-18 15:17 Jan Kratochvil
2011-07-18 16:52 ` Tom Tromey [this message]
2011-07-19 20:29   ` 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=m3vcuz7gea.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