Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Geoff Keating <geoffk@geoffk.org>
To: ac131313@cygnus.com
Cc: gcc-regression@gcc.gnu.org, gdb@sources.redhat.com,
	nathan@codesourcery.com
Subject: Re: 1 GCC regressions, 1 new, with your patch on 2001-07-21T09:30:01Z.
Date: Mon, 23 Jul 2001 22:11:00 -0000	[thread overview]
Message-ID: <200107240509.WAA02592@geoffk.org> (raw)
In-Reply-To: <3B5C9BF0.3040304@cygnus.com>

> Date: Mon, 23 Jul 2001 17:49:36 -0400
> From: Andrew Cagney <ac131313@cygnus.com>

> >> The new failures are:
> >> native gdb.sum gdb.base/selftest.exp:
> > 
> > 
> > This was interesting.  After two months, the GCC tree has finally been
> > stable for long enough for the tester to try to update its binutils
> > tree.  Unfortunately, this means it updates its _sources_, and it
> > turns out that selftest.exp requires you keep around the old gdb
> > sources so it can debug itself.
> > 
> > Since selftest.exp doesn't really test the compiler at all, I have
> > disabled it.
> 
> 
> I'm not sure what you mean,
> 
> As far as I know, selftest uses the just built native GDB to test the 
> just built native GDB.  The test being skipped when the just built GDB 
> isn't native (it doesn't make sense).  I think GCC should retain the 
> test since it is testing GDB against a very large program.

There is no "just-built" gdb.  GCC is tested against a known-working
gdb, built with the system compiler.

-- 
- Geoffrey Keating <geoffk@geoffk.org>


      reply	other threads:[~2001-07-23 22:11 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200107211225.f6LCPA730345@maat.cygnus.com>
2001-07-21  9:07 ` Geoff Keating
2001-07-21  9:34   ` remote gdb: reboot system(Linux) Michael S. Miles
2001-07-24  2:12     ` Amit S. Kale
2001-07-24 17:22       ` Andrew Cagney
2001-07-25  5:33         ` Amit S. Kale
2001-07-21 12:55   ` 1 GCC regressions, 1 new, with your patch on 2001-07-21T09:30:01Z Nathan Sidwell
2001-07-23 14:49   ` Andrew Cagney
2001-07-23 22:11     ` Geoff Keating [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=200107240509.WAA02592@geoffk.org \
    --to=geoffk@geoffk.org \
    --cc=ac131313@cygnus.com \
    --cc=gcc-regression@gcc.gnu.org \
    --cc=gdb@sources.redhat.com \
    --cc=nathan@codesourcery.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