From: Eli Zaretskii <eliz@is.elta.co.il>
To: kettenis@wins.uva.nl
Cc: gdb-patches@sources.redhat.com
Subject: Re: [PATCH] Unify i386 xm.h for FreeBSD and Linux
Date: Thu, 02 Aug 2001 08:24:00 -0000 [thread overview]
Message-ID: <200108021520.SAA04555@is.elta.co.il> (raw)
In-Reply-To: <200107311922.f6VJM9j21912@delius.kettenis.local>
> Date: Tue, 31 Jul 2001 21:22:09 +0200
> From: Mark Kettenis <kettenis@wins.uva.nl>
>
> This unifies the Linux and FreeBSD host configs. The idea of course
> is that xm-i386.h can be used by most of the other i386 hosts too.
>
> Checked in on mailine only.
Thanks, Mark. I committed today (head only) a corresponding change
for xm-go32.h. I attach it below, FYI.
Btw, why did you decide to define HOST_FLOAT_FORMAT and
HOST_DOUBLE_FORMAT explicitly? The defaults are on defs.h, and they
are identical to what you did. Any reason for that?
2001-08-02 Eli Zaretskii <eliz@is.elta.co.il>
* config/i386/xm-go32.h: Include xm-i386.h.
(HOST_BYTE_ORDER, HOST_LONG_DOUBLE_FORMAT): Remove definitions.
--- gdb/config/i386/xm-go32.h~0 Thu Jul 5 17:01:30 2001
+++ gdb/config/i386/xm-go32.h Thu Aug 2 17:30:36 2001
@@ -18,14 +18,9 @@
Foundation, Inc., 59 Temple Place - Suite 330,
Boston, MA 02111-1307, USA. */
-#define HOST_BYTE_ORDER LITTLE_ENDIAN
-
+#include "i386/xm-i386.h"
#include "fopen-bin.h"
#define GDBINIT_FILENAME "gdb.ini"
-
#define CRLF_SOURCE_FILES
-
#define DIRNAME_SEPARATOR ';'
-
-#define HOST_LONG_DOUBLE_FORMAT &floatformat_i387_ext
next prev parent reply other threads:[~2001-08-02 8:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-31 12:22 Mark Kettenis
2001-08-02 8:24 ` Eli Zaretskii [this message]
2001-08-02 10:33 ` Andrew Cagney
2001-08-02 11:39 ` Mark Kettenis
2001-08-02 13:17 ` Andrew Cagney
2001-08-02 11:14 ` Mark Kettenis
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=200108021520.SAA04555@is.elta.co.il \
--to=eliz@is.elta.co.il \
--cc=gdb-patches@sources.redhat.com \
--cc=kettenis@wins.uva.nl \
/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