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
next parent reply other threads:[~2000-06-24 6:01 UTC|newest]
Thread overview: 6+ 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 15:41 Re: Casandra Stevenson
2006-03-14 16:16 ` Re: Casandra Stevenson
2011-11-28 10:27 Belicov Alexei
[not found] <9349E3C2-200B-4F80-BBDE-39A2EC100C05@ug.edu.ec>
[not found] ` <B5A31154-AC7D-46FE-B6D5-CCE04E129C46@ug.edu.ec>
[not found] ` <BN8PR01MB5572AEC9EC4A96E34B333B38AB059@BN8PR01MB5572.prod.exchangelabs.com>
[not found] ` <BN8PR01MB5572F4B3AC24435A2F0FBEAFAB059@BN8PR01MB5572.prod.exchangelabs.com>
[not found] ` <BN8PR01MB557272E7EF34C0A705491926ABF09@BN8PR01MB5572.prod.exchangelabs.com>
2022-12-30 15:28 ` RE: KEYLA PORTES JAMA
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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).