Re: recent dejagnu changes

Geoff Keating
2000-08-08T14:24:00Z

> Date: Tue, 08 Aug 2000 12:52:32 -0700
> From: Stan Shebs <shebs@apple.com>

> Since we all have a common interest in making dejagnu work well,
> and no benevolent dejagnu dictator to force us to get along :-),
> let's try to help each other here.

Unfortunately, I've been told that all further communication with
Jimmy should go through our HP person, Jim Blandy. So any help with
dejagnu is going to have to come from them or be properly scheduled.

In the meantime, I've switched my automated tester to manual mode for
combined-tree integration, and made its heuristics more paranoid. If
I find dejagnu breaks again, I'll just freeze it at the
last-known-good version. Hopefully this will limit the damage.
--
- Geoffrey Keating <geoffk@cygnus.com>
From ac131313@cygnus.com Tue Aug 08 15:42:00 2000
From: Andrew Cagney <ac131313@cygnus.com>
To: Eli Zaretskii <eliz@is.elta.co.il>
Cc: robert.hoehne@gmx.net, gdb-patches@sourceware.cygnus.com
Subject: Re: Problems with i386_register_convert_to_virtual
Date: Tue, 08 Aug 2000 15:42:00 -0000
Message-id: <39908C0B.C9F5E165@cygnus.com>
References: <200008052252.AAA22962@robby.dittmannsdorf.de> <200008060851.KAA23990@robby.dittmannsdorf.de> <200008080644.CAA02415@indy.delorie.com>
X-SW-Source: 2000-08/msg00160.html
Content-length: 801

Eli Zaretskii wrote:
>
> > From: Robert Hoehne <robert.hoehne@gmx.net>
> > Date: Sun, 6 Aug 2000 10:52:41 +0200
> >
> > After more searching in the GDB code and docs, I found the macro
> > REGISTER_CONVERTIBLE which tells, if a register have different
> > raw and virtual sizes. This macro is also used for instance in findvar.c
> > to decide, if REGISTER_CONVERT_TO_VIRTUAL is called or a
> > simple memcpy is done. In my Opionion either this should be documented
> > in the description for REGISTER_CONVERT_TO_VIRTUAL that
> > this macro should be called only, when REGISTER_CONVERTIBLE
> > returns true, or that logic should be included in the convert macro.
>
> I agree. Does anyone have preferences as to what way of these two is
> the best?

I'd suggest adjusting the documentation.

Andrew
From ac131313@cygnus.com Tue Aug 08 16:53:00 2000
From: Andrew Cagney <ac131313@cygnus.com>
To: Geoff Keating <geoffk@cygnus.com>
Cc: guo@cup.hp.com, fnasser@cygnus.com, gdb-patches@sourceware.cygnus.com
Subject: Re: recent dejagnu changes
Date: Tue, 08 Aug 2000 16:53:00 -0000
Message-id: <39909BD0.522545A3@cygnus.com>
References: <Pine.LNX.4.10.10008080958530.12236-100000@hpcll168.cup.hp.com> <200008081827.LAA06137@localhost.cygnus.com>
X-SW-Source: 2000-08/msg00161.html
Content-length: 792

Geoff,

I don't know that pulling Jimmy's dejagnu patch was the best thing to
do. In a way it is like me pulling a G++ patch just because it has (yet
again :-) broken the GDB/C++ testsuites. If I did that I'd be
(understandably) hounded out of town by the GCC team :-(. Instead, what
one would hope would happen is \x12 that the groups try to co-operate and
resolve problems as soon as they are found. If the GDB team find
problems they push patches back to GCC.

For DEJAGNU, checking that a change regresses none of GDB, GCC or
BINUTILS would be a good thing (tm). However, as things currently
stand, this not straight forward. Instead we are reliant on people,
such as yourself, identifying problems and reporting them so that they
can be fixed (and not reverted :-).

enjoy,
Andrew
From ac131313@cygnus.com Tue Aug 08 17:00:00 2000
From: Andrew Cagney <ac131313@cygnus.com>
To: Jimmy Guo <guo@cup.hp.com>
Cc: Fernando Nasser <fnasser@cygnus.com>, Geoff Keating <geoffk@cygnus.com>, gdb-patches@sourceware.cygnus.com
Subject: Re: [RFA] dejagnu runtest.exp redundant testing
Date: Tue, 08 Aug 2000 17:00:00 -0000
Message-id: <39909DE1.82CB4FB8@cygnus.com>
References: <Pine.LNX.4.10.10008071129160.5575-100000@hpcll168.cup.hp.com>
X-SW-Source: 2000-08/msg00162.html
Content-length: 943

Jimmy,

As an asside, you (and others) may be interested in the attatched
files. It lets you use CVSup to create a merged tree. It may be
possible to build / test it - no promises though!

Andrew
*default date=.
all delete release=toplev list=toplev compress prefix=all host=sourceware.cygnus.com compress tag=.
all delete release=bfd list=bfd compress prefix=all host=sourceware.cygnus.com compress tag=.
all delete release=gdb list=gdb compress prefix=all host=sourceware.cygnus.com compress tag=.
all delete release=binutils list=binutils compress prefix=all host=sourceware.cygnus.com compress tag=.
all delete release=gcc list=gcc compress prefix=all host=sourceware.cygnus.com compress tag=.
all delete release=dejagnu list=dejagnu compress prefix=all host=sourceware.cygnus.com compress tag=.
all delete release=newlib list=newlib compress prefix=all host=sourceware.cygnus.com compress tag=.
From guo@cup.hp.com Tue Aug 08 17:04:00 2000
From: Jimmy Guo <guo@cup.hp.com>
To: Andrew Cagney <ac131313@cygnus.com>
Cc: Geoff Keating <geoffk@cygnus.com>, fnasser@cygnus.com, gdb-patches@sourceware.cygnus.com
Subject: Re: recent dejagnu changes
Date: Tue, 08 Aug 2000 17:04:00 -0000
Message-id: <Pine.LNX.4.10.10008081655480.13431-100000@hpcll168.cup.hp.com>
References: <39909BD0.522545A3@cygnus.com>
X-SW-Source: 2000-08/msg00163.html
Content-length: 785

If I may, let's retire this thread ... there're assumptions and
perceptions I made, both in the dejagnu design and in the working
process, that caused the dejagnu regression and the following
communications that's less than desirable ... and my apologies to the
GCC project which wasted time tracking my changes down :)

Changes to odd components like dejagnu with little documentation nor
visibility (until it breaks) are dangerous. Fortunately I don't have
further changes in this area ... as to the couple of patches, I'm sure
we can work it through without further disturbance. It's never too much
to be reminded that working on a OpenSource project requires extra
prudence and patience ... which is something the HP WDB team is prepared
to accept.

- Jimmy Guo, guo@cup.hp.com