From: Mark Kettenis <kettenis@wins.uva.nl>
To: takis@XFree86.Org
Cc: gdb@sourceware.cygnus.com
Subject: Re:
Date: Sat, 24 Jun 2000 06:01:00 -0000 [thread overview]
Message-ID: <200006241301.e5OD1gm00437@delius.kettenis.local> (raw)
In-Reply-To: <Pine.BSF.4.05.10006221115120.1946-100000@public.xfree86.org>
Date: Thu, 22 Jun 2000 11:26:04 -0700 (PDT)
From: Takis Psarogiannakopoulos <takis@XFree86.Org>
Dear Mark,
Thank you for answering this. Yes I know that FPU regs are short ints
(some of them) and I use the correct structs when I want to print
them. However by adding to i386dgux.mt the file i387-tdep.o we have an
immediate problem. It doesnt compile as it needs defs such as
FCOFF_REGNUM etc ... so there the question what is what.
That is where my e-mail was targetting. For the story I have ported
gdb-4.18 to DG/UX and sources are in ftp.xfree86.org
pub/XFree86/3.3.6/binaries/DGUX-ix86/GDB_BETA. (if you have time
take a look in the file there gdb/i386dgux-nat.c to verify that
I ma treating correctll the fpu regs). That port (fully working)
never make it to the oficcial 5.0 for several reasons (mailnly I had not
the time to request and sign copyright assignments for the *several* parts
of gdb as bfd, etc etc ...!
I've taken a look at the stuff now. However, since the FPU stuff is
rather different in 5.0, I don't think it's very useful to comment on
the way you handle things in your 4.18 based port. If you follow my
advice you shouldn't have to do any significant manipulations on the
FPU state at all, and you could remove most of your home-grown FPU
stuff from i386dgux-nat.c.
It would be great if you could contribute your DG/UX port back to the
FSF. Indeed we need a copyright assignment first. If you can find
the time to do them, please do so ASAP. They take some time being
processed.
Before we can integrate your DG/UX port into the official GDB tree,
some bits will have to be cleaned up. First of all, you'll have to
base your work on the current development version. Working from
snapshots is fine, but working from CVS is much more convenient.
Right now there is quite a bit of code duplication, and we'll have to
try to reduce that a bit. You've alse added some DG/UX-specific
#ifdefs that will have to be eliminated. I'll be happy to work
together on those issues.
Now since I dont have CVS I would be greatfull if you send the files
i387-nat.c and latest i386bsd.c ...
Since you told me you downloaded a recent snapshot, you probably
already have them. If you still need those files, drop me a mail.
Mark
From takis@XFree86.Org Sun Jun 25 06:30:00 2000
From: Takis Psarogiannakopoulos <takis@XFree86.Org>
To: kettenis@wins.uva.nl
Cc: gdb@sourceware.cygnus.com
Subject: RE:Re:
Date: Sun, 25 Jun 2000 06:30:00 -0000
Message-id: <Pine.BSF.4.05.10006250624510.26196-100000@public.xfree86.org>
X-SW-Source: 2000-06/msg00180.html
Content-length: 2839
Hi Mark,
On Sat, 24 Jun 2000, Mark Kettenis wrote:
> I've taken a look at the stuff now. However, since the FPU stuff is
> rather different in 5.0, I don't think it's very useful to comment on
> the way you handle things in your 4.18 based port. If you follow my
> advice you shouldn't have to do any significant manipulations on the
> FPU state at all, and you could remove most of your home-grown FPU
> stuff from i386dgux-nat.c.
Thats what I have done for the 5.0 release. I have integrate the routines
of i387-nat.c into i386dgux-nat.c (no i387-nat.c in 5.0) and remove most
of the floating point info handling code.
> It would be great if you could contribute your DG/UX port back to the
> FSF. Indeed we need a copyright assignment first. If you can find
> the time to do them, please do so ASAP. They take some time being
> processed.
I wouldnt have any problem to give free the code to FSF. If this
worth something, I am declaring here publickly that the code in
ftp.xfree.org is *free* and anyone is welcome to integrate it as he/she
finds appropriate to future gdb releases. In gdb-5.0 port there are
two main additions/changes:
1) Full support for pthreads (I am desperate for that)
2) A much better port of bfd that allows also binutils-2.9.1 to work
for DG/UX unix and build gnu-as and most importantly gnu-ld.
However all these are done with #ifdefs DGUX ... (mainly in bfd).
> Before we can integrate your DG/UX port into the official GDB tree,
> some bits will have to be cleaned up. First of all, you'll have to
> base your work on the current development version. Working from
> snapshots is fine, but working from CVS is much more convenient.
> Right now there is quite a bit of code duplication, and we'll have to
> try to reduce that a bit. You've alse added some DG/UX-specific
> #ifdefs that will have to be eliminated. I'll be happy to work
> together on those issues.
After finishing release 5.0-port we can have a go on that. If anything
it will allow me to not deal anymore so extensively with the gdb
port (from the moment that the code will be integrated in say 5.01).
Only things from then and on will be "building issues" but these can
be dealt also by ordinary DG/UX users that will watch your list and
have a go to build gdb snapshots.
> Since you told me you downloaded a recent snapshot, you probably
> already have them. If you still need those files, drop me a mail.
>
That is correct. I have seen the files now.
Regards,
Takis
PS: I am cc'ing the gdb list but ... your server has some problem:
> The IP number that I'm denying mail from is 204.152.184.37
> The list that you're on is ORBS. See:
> http://www.orbs.org/verify.cgi?address=204.152.184.37
> for more information about this list and why you are on it.
public.xfree86.org is certainly not the ORBS list ...
next parent reply other threads:[~2000-06-24 6:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.BSF.4.05.10006221115120.1946-100000@public.xfree86.org>
2000-06-24 6:01 ` Mark Kettenis [this message]
2004-10-29 17:52 Re: ewright
2006-03-14 16:16 Re: Casandra Stevenson
2006-03-14 15:41 ` Re: Casandra Stevenson
2011-11-28 10:27 Belicov Alexei
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=200006241301.e5OD1gm00437@delius.kettenis.local \
--to=kettenis@wins.uva.nl \
--cc=gdb@sourceware.cygnus.com \
--cc=takis@XFree86.Org \
/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