From: Sami Wagiaalla <swagiaal@redhat.com>
To: gdb-patches@sourceware.org
Subject: Re: [RFA 2/4] dwarf2_physname
Date: Tue, 24 Nov 2009 19:20:00 -0000 [thread overview]
Message-ID: <4B0C322E.7070503@redhat.com> (raw)
In-Reply-To: <20091123170710.GA15216@caradoc.them.org>
On 11/23/2009 12:07 PM, Daniel Jacobowitz wrote:
> On Mon, Nov 23, 2009 at 08:51:16AM -0800, Keith Seitz wrote:
>> On 11/20/2009 02:09 PM, Daniel Jacobowitz wrote:
>>
>>> I am generally opposed to committing known regressions. If there are
>>> supporting patches we need to get in first, let's do that; if there
>>> are tests we decide to break, let's XFAIL or KFAIL them. That's the
>>> only way we can make the testsuite more useful.
>>
>> Sami has a follow-on patch that he could submit to fix all of these
>> tests (they all pass on archer-keiths-expr-cumulative). Perhaps it
>> would be acceptable for Sami to submit that patchset when/if this
>> patch is accepted? [His patches rely on this patchset.]
>
> If it applies on top of this, could he post it now? Then we can treat
> them as a unit for review and testing purposes.
>
I looked into this. It turns out that this is fixed by the patches
posted on the thread rooted at this message
http://sourceware.org/ml/gdb-patches/2009-07/msg00305.html
Applying these patches prior to applying Keith's fixes the namespace.exp
issues.
Note: parts of keiths patch to do with removing references to linkage
name from cp-support, cp-namespace.c, valops.c give rise to conflicts so
I just remove those manually.
Sami
next prev parent reply other threads:[~2009-11-24 19:20 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-20 21:20 Keith Seitz
2009-11-20 22:10 ` Daniel Jacobowitz
2009-11-21 0:04 ` Tom Tromey
2009-11-21 3:46 ` Frank Ch. Eigler
2009-11-23 18:06 ` Tom Tromey
2009-11-23 19:00 ` Daniel Jacobowitz
2009-11-23 16:52 ` Keith Seitz
2009-11-23 17:08 ` Daniel Jacobowitz
2009-11-24 19:20 ` Sami Wagiaalla [this message]
2010-01-27 17:10 ` Sami Wagiaalla
2009-12-08 19:47 ` Keith Seitz
2009-12-14 19:33 ` Keith Seitz
2009-12-17 20:19 ` Tom Tromey
2009-12-17 20:28 ` Daniel Jacobowitz
2009-12-17 22:39 ` Paul Pluzhnikov
2009-12-22 18:35 ` Tom Tromey
2009-12-22 19:24 ` Daniel Jacobowitz
2010-01-20 20:37 ` Keith Seitz
2010-01-26 21:17 ` Daniel Jacobowitz
2010-01-27 19:12 ` Keith Seitz
2010-01-28 20:22 ` Keith Seitz
2010-01-28 20:24 ` Daniel Jacobowitz
2010-01-28 23:41 ` Keith Seitz
2010-02-01 16:48 ` Daniel Jacobowitz
2010-02-01 19:32 ` Keith Seitz
2010-02-01 19:39 ` Daniel Jacobowitz
2010-02-01 21:52 ` Keith Seitz
2010-02-01 22:19 ` Daniel Jacobowitz
2010-02-02 23:23 ` Keith Seitz
2010-02-02 23:31 ` Keith Seitz
2010-02-03 2:46 ` Daniel Jacobowitz
2010-02-04 17:48 ` Tom Tromey
2010-02-04 18:14 ` Daniel Jacobowitz
2010-02-05 17:13 ` Keith Seitz
2010-02-05 17:29 ` Daniel Jacobowitz
2010-02-05 20:24 ` Keith Seitz
2010-02-05 20:57 ` Daniel Jacobowitz
2010-02-05 23:10 ` Keith Seitz
2010-02-05 23:46 ` Daniel Jacobowitz
2010-02-04 17:21 ` Tom Tromey
2010-02-04 17:25 ` Daniel Jacobowitz
2009-11-23 7:31 ` André Pönitz
2009-11-23 16:57 ` Keith Seitz
2009-11-23 17:20 ` Tom Tromey
2009-11-24 7:22 ` André Pönitz
2009-11-24 22:54 ` Tom Tromey
2009-11-25 9:16 ` André Pönitz
2009-11-25 18:14 ` Tom Tromey
2009-11-23 17:15 ` Tom Tromey
2009-11-24 22:11 ` Joel Brobecker
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=4B0C322E.7070503@redhat.com \
--to=swagiaal@redhat.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