Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andrew Burgess <aburgess@redhat.com>
To: Tom Tromey <tom@tromey.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCHv3] gdb: remove attempted type de-duplication when building gdb-index
Date: Thu, 13 Nov 2025 16:32:04 +0000	[thread overview]
Message-ID: <87o6p5zyez.fsf@redhat.com> (raw)
In-Reply-To: <87cy6fkltn.fsf@tromey.com>

Tom Tromey <tom@tromey.com> writes:

>>>>>> "Andrew" == Andrew Burgess <aburgess@redhat.com> writes:
>
> Andrew> In v3:
> Andrew>   - Fixed test failure in gdb.cp/stub-array-size.exp when using
> Andrew>     cc-with-gdb-index, using more recent versions of gcc.  This did
> Andrew>     require additional changes in dwarf2/read-gdb-index.c, and removal
> Andrew>     of a test that is now out of date.  The commit message has been
> Andrew>     updated with a full description.
>
> Thanks.  I think this is ok.  See below for commentary but there's
> nothing you need to change.
>
> Approved-By: Tom Tromey <tom@tromey.com>

With this patch now merged:

  https://inbox.sourceware.org/gdb-patches/c7599a8d2d8408eafd08919e77dd6e31309b55e1.1762874404.git.aburgess@redhat.com

I've rebased this work, updated the test a little to take account of the
improved 'info types' output, and pushed this patch.

Thanks,
Andrew


      parent reply	other threads:[~2025-11-13 16:32 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-02  9:36 [PATCH] " Andrew Burgess
2025-10-16 18:11 ` [PATCHv2] " Andrew Burgess
2025-10-21 13:45   ` [PATCHv3] " Andrew Burgess
2025-10-22 15:17     ` Tom Tromey
2025-10-22 15:59       ` Andrew Burgess
2025-10-22 16:13         ` Andrew Burgess
2025-10-22 17:21           ` Tom Tromey
2025-11-04 14:23             ` Andrew Burgess
2025-10-22 17:21         ` Tom Tromey
2025-11-13 16:32       ` Andrew Burgess [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=87o6p5zyez.fsf@redhat.com \
    --to=aburgess@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=tom@tromey.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