From: "Kris Warkentin" <kewarken@qnx.com>
To: <gdb-patches@sources.redhat.com>
Subject: Re: [patch] i386-nto (QNX Neutrino) support
Date: Wed, 23 Apr 2003 23:02:00 -0000 [thread overview]
Message-ID: <004b01c309e6$4f768000$0202040a@catdog> (raw)
In-Reply-To: <0b2c01c309c8$ebafebf0$0202040a@catdog>
Please disregard this patch for now. Daniel just gave me some ideas for a
way to restructure it and remove the dependancy on the debug.h header.
cheers,
Kris
----- Original Message -----
From: "Kris Warkentin" <kewarken@qnx.com>
To: <gdb-patches@sources.redhat.com>
Sent: Wednesday, April 23, 2003 2:48 PM
Subject: [patch] i386-nto (QNX Neutrino) support
> In the interest of expediency, I removed the non-i386 things from debug.h
> which I believe eliminates the portability issues. These can be
re-examined
> later when I'm doing the mips/powerpc ports.
>
> Most of this stuff has been gone over by Mark Kettenis fairly extensively
(I
> ran indent again Mark) and I hope that the debug.h issue was the last of
> them. I've attached a diff of the config files as well as all the
> individual files. I also included a tarball that can be extracted in the
> gdb directory.
>
> Thanks
>
> Kris
>
> ChangeLog
>
> * configure.tgt: Add i386nto target
> * i386-nto-tdep.c: New file. i386 specific support for QNX Neutrino.
> * nto-tdep.c: New file. Neutrino target support routines.
> * nto-tdep.h: New file. Neutrino target header.
> * config/tm-qnxnto.h: New file.
> * config/i386/i386nto.mt: New file.
> * config/i386/tm-i386nto.h: New file.
> * nto-share/debug.h: New file. Neutrino procfs interface.
>
next prev parent reply other threads:[~2003-04-23 22:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-23 19:42 Kris Warkentin
2003-04-23 23:02 ` Kris Warkentin [this message]
2003-04-23 23:32 ` [patch-2] " Kris Warkentin
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='004b01c309e6$4f768000$0202040a@catdog' \
--to=kewarken@qnx.com \
--cc=gdb-patches@sources.redhat.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