Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Doug Evans <xdje42@gmail.com>
To: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [PATCH 00/21] struct symtab split part 2
Date: Tue, 18 Nov 2014 09:06:00 -0000	[thread overview]
Message-ID: <CAP9bCMR79US3oaSVqdg3HhGW5KZ4EV9UmuVgQuGminqp+QBzGw@mail.gmail.com> (raw)
In-Reply-To: <CAP9bCMTvXnj+hVciZgfLjZDTEYGp0ogD5+SvrFhU_COLdGVnFg@mail.gmail.com>

On Sat, Nov 15, 2014 at 9:34 PM, Doug Evans <xdje42@gmail.com> wrote:
> On Thu, Nov 13, 2014 at 4:48 AM, Doug Evans <xdje42@gmail.com> wrote:
>> Hi.
>>
>> This is part 2 of a patch set to split up struct symtab.
>> Part 1 was here: https://sourceware.org/ml/gdb-patches/2014-11/msg00193.html
>>
>> [...]
>>
>> Regression tested on amd64-linux with dwarf and with/without gdb_index,
>> and also with stabs.  And also x86_64-w64-mingw32 as a cross-debugger.
>> And built with --enable-targets=all.
>> It needs testing on other file formats as well, can anyone do xcoff?
>>
>> A tree with all patches is available here:
>> git@github.com:xdje42/gdb.git, branch "symtabs"
>
> I've finished regression testing with my m32r-coff port.
> [The port isn't complete enough to do exhaustive testing, but it does
> cover a lot.]
>
> IWBN to test with xcoff.
> Hopefully my application for gcc compiler farm access will be granted soon.

I've finished xcoff testing via the gcc compile farm.
No regressions so far.
My plan is to commit this by Thursday of this week (barring anything
that comes up).


  reply	other threads:[~2014-11-18  9:06 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-13 12:49 Doug Evans
2014-11-13 16:13 ` Simon Marchi
2014-11-14 17:19   ` Doug Evans
2014-11-16  5:34 ` Doug Evans
2014-11-18  9:06   ` Doug Evans [this message]
2014-11-18 15:38     ` Pedro Alves
2014-11-20 15:51       ` Doug Evans
2014-11-23 19:22         ` Doug Evans

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=CAP9bCMR79US3oaSVqdg3HhGW5KZ4EV9UmuVgQuGminqp+QBzGw@mail.gmail.com \
    --to=xdje42@gmail.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