From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gdb-return-8697-listarch-gdb=sourceware.cygnus.com@sources.redhat.com>
Received: (qmail 15972 invoked by alias); 26 Apr 2002 18:54:43 -0000
Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm
Precedence: bulk
List-Subscribe: <mailto:gdb-subscribe@sources.redhat.com>
List-Archive: <http://sources.redhat.com/ml/gdb/>
List-Post: <mailto:gdb@sources.redhat.com>
List-Help: <mailto:gdb-help@sources.redhat.com>, <http://sources.redhat.com/ml/#faqs>
Sender: gdb-owner@sources.redhat.com
Received: (qmail 15905 invoked from network); 26 Apr 2002 18:54:42 -0000
Received: from unknown (HELO duracef.shout.net) (204.253.184.12)
  by sources.redhat.com with SMTP; 26 Apr 2002 18:54:42 -0000
Received: (from mec@localhost)
	by duracef.shout.net (8.11.6/8.11.6) id g3QIseC16849;
	Fri, 26 Apr 2002 13:54:40 -0500
Date: Fri, 26 Apr 2002 11:54:00 -0000
From: Michael Elizabeth Chastain <mec@shout.net>
Message-Id: <200204261854.g3QIseC16849@duracef.shout.net>
To: ezannoni@redhat.com, gdb@sources.redhat.com
Subject: Re: Adding target specific tests
X-SW-Source: 2002-04/txt/msg00466.txt.bz2

gdb.altivec is my favorite.
gdb.powerpc is my second choice.
gdb.regs and gdb.abi don't sound good to me.

I kinda like this:

  gdb.base, gdb.gdb, gdb.mi, gdb.threads, gdb.trace
  gdb.arch.altivec, gdb.arch.hp
  gdb.format.stabs
  gdb.lang.asm, gdb.lang.c++, gdb.lang.chill, gdb.lang.disasm,
  gdb.lang.fortran, gdb.lang.java

But that would fail the 8.3 uniqueness test.

Or this:

  gdb.base
  gdb.gdb
  gdb.mi
  gdb.threads
  gdb.trace
  gdb.arch/
    altivec
    hp
  gdb.format/
    stabs
  gdb.lang/
    asm
    c++
    chill
    disasm
    fortran
    java

... but that might mess up somebody's scripts somewhere.

Indeed, any directory reorganization would impair my ability to
compare 5.2 with 5.3 when it comes time to release 5.3.

Michael C