Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Denis Joseph Barrow" <DJBARROW@de.ibm.com>
To: Andrew Cagney <ac131313@cygnus.com>
Cc: gdb-patches@sourceware.cygnus.com
Subject: Re: New gdb 31 & 64 bit patches for S/390
Date: Mon, 13 Aug 2001 09:47:00 -0000	[thread overview]
Message-ID: <OF893FDF35.62738920-ONC1256AA7.005BD133@de.ibm.com> (raw)

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1661 bytes --]

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





             reply	other threads:[~2001-08-13  9:47 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-13  9:47 Denis Joseph Barrow [this message]
     [not found] <OFEFF0AD94.761C34C1-ONC1256AB6.005503EE@de.ibm.com>
2001-08-28 16:33 ` Daniel Jacobowitz
2001-09-05 21:45   ` Andrew Cagney
  -- strict thread matches above, loose matches on Subject: below --
2001-08-15  2:22 Denis Joseph Barrow
2001-08-15  9:03 ` Andrew Cagney
2001-08-15  9:54 ` Andrew Cagney
2001-08-13  3:06 Denis Joseph Barrow
2001-08-13  9:31 ` Andrew Cagney
2001-07-06  2:31 Denis Joseph Barrow
2001-07-05 10:24 Denis Joseph Barrow
2001-07-05 12:46 ` Andrew Cagney
2001-07-08  0:53   ` Eli Zaretskii
2001-07-08 19:23     ` Andrew Cagney
2001-07-05  9:19 Denis Joseph Barrow
2001-07-05 12:36 ` Andrew Cagney
2001-07-05  9:15 Denis Joseph Barrow
2001-07-05  5:04 Denis Joseph Barrow
2001-07-05  3:57 Denis Joseph Barrow
2001-07-05 10:11 ` Andrew Cagney
2001-07-05 10:11 ` Andrew Cagney
2001-07-05  3:12 Denis Joseph Barrow
2001-06-18  3:32 DJBARROW
     [not found] <C1256A02.00573066.00@d12mta09.de.ibm.com>
2001-03-01 10:39 ` Nick Clifton
2001-03-01  2:50 DJBARROW
2001-03-01 10:37 ` Nick Clifton
2001-02-27 12:39 DJBARROW
2001-02-28 16:13 ` Nick Clifton
2001-06-15  9:53 ` Andrew Cagney
2001-06-15 11:46   ` Andreas Jaeger
2001-06-15 12:22     ` Andrew Cagney
2001-07-04 11:25 ` Andrew Cagney
2001-07-04 21:02 ` Andrew Cagney
2001-07-04 21:02 ` Andrew Cagney
2001-07-04 21:02 ` Andrew Cagney

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=OF893FDF35.62738920-ONC1256AA7.005BD133@de.ibm.com \
    --to=djbarrow@de.ibm.com \
    --cc=ac131313@cygnus.com \
    --cc=gdb-patches@sourceware.cygnus.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