Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Doug Evans <dje@google.com>
To: gdb-patches@sourceware.org
Subject: Re: [patch] fix exp/12117
Date: Wed, 13 Oct 2010 18:03:00 -0000	[thread overview]
Message-ID: <AANLkTimccBCvpkzYirh8VxrkN=2QdsmxS=a+5VSZD61g@mail.gmail.com> (raw)
In-Reply-To: <20101013175308.17B772461AE@ruffy.mtv.corp.google.com>

On Wed, Oct 13, 2010 at 10:53 AM, Doug Evans <dje@google.com> wrote:
> Hi.
>
> This patch fixes pr exp/12117.
> http://sourceware.org/bugzilla/show_bug.cgi?id=12117
>
> I will check this in in two days if there are no objections.
>
> 2010-10-13  Doug Evans  <dje@google.com>
>
>        PR exp/12117
>        * c-typeprint.c (c_print_type): Call CHECK_TYPEDEF after calling
>        c_type_print_base.
>        (c_type_print_modifier_flags): New function.
>        (c_type_print_modifier): Call it.
>        (c_type_print_base): Collect instance_flags while we're stripping
>        typedefs.  Change calls to c_type_print_modifier to call
>        c_type_print_modifier_flags instead.
>        (c_type_print_base, case TYPE_CODE_TYPEDEF): Verify assumptions of
>        when this case happens.  Print "<unnamed typedef>".
>        * gdbtypes.h (strip_typedefs): Declare.
>        * gdbtypes.c (strip_typedefs): New function.
>        (check_typedef): Call it.
>
>        testsuite/
>        * gdb.cp/pr12117.cc: New file.
>        * gdb.cp/pr12117.exp: New file.

Blech, I told myself not to forget adding this note this time ... :-(

Tested on amd64-linux, no regressions.


  reply	other threads:[~2010-10-13 18:03 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-13 17:53 Doug Evans
2010-10-13 18:03 ` Doug Evans [this message]
2010-10-13 18:44 ` Tom Tromey
2010-10-13 18:55   ` Doug Evans
2010-10-13 19:04     ` Tom Tromey
2010-10-13 20:55       ` Doug Evans
2010-10-13 21:10       ` Jan Kratochvil
2010-10-14  1:55         ` Doug Evans
2010-10-14  9:35           ` Jan Kratochvil
2010-10-15 17:42             ` Tom Tromey
2010-10-15 17:49               ` Jan Kratochvil
2010-10-15 17:41         ` 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='AANLkTimccBCvpkzYirh8VxrkN=2QdsmxS=a+5VSZD61g@mail.gmail.com' \
    --to=dje@google.com \
    --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