Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Mark Kettenis <mark.kettenis@xs4all.nl>
Cc: gdb-patches@sourceware.org
Subject: Re: [ob] Adjust member pointer test for g++ 3.3
Date: Sun, 28 Jan 2007 17:52:00 -0000	[thread overview]
Message-ID: <20070128175248.GA17887@nevyn.them.org> (raw)
In-Reply-To: <200701281750.l0SHo5m1025254@brahms.sibelius.xs4all.nl>

On Sun, Jan 28, 2007 at 06:50:05PM +0100, Mark Kettenis wrote:
> > Hmm... how much of a hack do you think it's worth? :-)  It's definitely
> > possible.
> > 
> > The problem is that this is a perfectly legitimate piece of debug
> > output, describing "int A::**" instead of "int A::*".  We could
> > recognize this problem based on string matching the DW_AT_producer;
> > I have added precedents for that before.  I don't see any other way
> > of doing it.
> 
> I don't really care; ok if I xfail those tests for GCC 3.3.x?  3.4.x
> seems to be fine.  Did you test things on some other GCC versions?

That's fine with me.  I believe I tested a 3.4.x gcc and a 4.1.x.

> Oops, for some reason I thought this was a new test.  Anyway, the
> failure modes are probably completely different after your code
> changes, so removing them is probably the most sensible thing to do.

It actually was originally an HP aCC test.  You're right - I should
delete the kfails, although I have honestly no idea what the test will
do for stabs.

-- 
Daniel Jacobowitz
CodeSourcery


      reply	other threads:[~2007-01-28 17:52 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-12 20:17 Daniel Jacobowitz
2007-01-12 21:50 ` Mark Kettenis
2007-01-12 23:08   ` Daniel Jacobowitz
2007-01-28 15:40     ` Mark Kettenis
2007-01-28 17:11       ` Daniel Jacobowitz
2007-01-28 17:50         ` Mark Kettenis
2007-01-28 17:52           ` Daniel Jacobowitz [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=20070128175248.GA17887@nevyn.them.org \
    --to=drow@false.org \
    --cc=gdb-patches@sourceware.org \
    --cc=mark.kettenis@xs4all.nl \
    /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