This is the mail archive of the
gdb-patches@sources.redhat.com
mailing list for the GDB project.
Re: New gdb 31 & 64 bit patches for S/390
- To: Andrew Cagney <ac131313 at cygnus dot com>
- Subject: Re: New gdb 31 & 64 bit patches for S/390
- From: "Denis Joseph Barrow" <DJBARROW at de dot ibm dot com>
- Date: Mon, 13 Aug 2001 18:45:17 +0200
- Cc: gdb-patches at sourceware dot cygnus dot com
Andrew do you realise I've done over 500 hours work just jumping through
hoops for you & nearly no work on any real improvment to the code.
To be quite honest I'm quite fed up with it.
No wonder you lost the HP maintainer.
D.J. Barrow Gnu/Linux for S/390 kernel developer
eMail: djbarrow@de.ibm.com,barrow_dj@yahoo.com
Phone: +49-(0)7031-16-2583
IBM Germany Lab, Schönaicherstr. 220, 71032 Böblingen
Andrew Cagney <ac131313@cygnus.com> on 13.08.2001 18:30:55
Please respond to Andrew Cagney <ac131313@cygnus.com>
To: Denis Joseph Barrow/Germany/Contr/IBM@IBMDE
cc: gdb-patches@sourceware.cygnus.com
Subject: Re: New gdb 31 & 64 bit patches for S/390
> Hi Andrew,
> I basically took this stuff from other architectures on gdb-5.0, I
presume
> they knew what they were doing &
> something subtle would break if I didn't do it, I'm using the same source
> base for the latest stuff & gdb-5.0
> as much as possible to avoid maintaining 2 different incomatible source
> bases.
Ah, it is actually much simpler - many of the existing NM and XM files
are wrong. Their problems, I suspect, date back to when there weren't
NM/XM files and when the need to do the two correctly was less
important. From there, as with many parts of gdb, the problem just spread.
Anyway, people have been activly cleaning up the problem.
> So some definitions specific to gdb-5.0 ( which isn't multiarch capible )
> will stay in /config/s390 header files
> until gdb-5.1 or whatever is officially released.
Please dont. The GDB trunk shouldn't be used as a holding area for code
only used on old branches. That is what old branches are for.
Andrew