Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@mvista.com>
To: gdb-patches@sources.redhat.com
Subject: Re: [RFA] Remove some obsolete gcc xfails from overload.exp
Date: Mon, 07 Jan 2002 13:24:00 -0000	[thread overview]
Message-ID: <20020107162510.A31845@nevyn.them.org> (raw)
In-Reply-To: <200201072108.g07L8ps30440@fred.ninemoons.com>

On Mon, Jan 07, 2002 at 02:08:51PM -0700, Fred Fish wrote:
> Some of the gcc xfails in overload.exp seem to be obsolete.  The
> xfailed tests currently pass with the development gdb using the latest
> development gcc, and also with the released gdb-5.1.0.1 using the
> released gcc-3.0.3.

[I can't approve this, but...] these look right to me.  I'm going to
try to fix the remainder of the XFAILS in this file; we shouldn't be
botching any of them.  I fixed most of these tests several weeks ago;
thanks for updating the testsuite.


-- 
Daniel Jacobowitz                           Carnegie Mellon University
MontaVista Software                         Debian GNU/Linux Developer


      reply	other threads:[~2002-01-07 21:24 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-07 13:10 Fred Fish
2002-01-07 13:24 ` 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=20020107162510.A31845@nevyn.them.org \
    --to=drow@mvista.com \
    --cc=gdb-patches@sources.redhat.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