From: Doug Evans <dje@google.com>
To: gdb-patches@sourceware.org, joel.sherrill@oarcorp.com
Subject: [PATCH] Remove i386bsd-tdep.o from x86_64-*-elf* target
Date: Fri, 25 Mar 2016 16:30:00 -0000 [thread overview]
Message-ID: <94eb2c0bbbf28763bf052ee215f4@google.com> (raw)
Hi all.
I'm currently working on an x86_64 "bare metal" target and am finding
various problems (patches to follow once I get things cleaned up).
In the process of cleaning things up, I'd like to make the following patch.
It's wrong to have bsd-anything (or linux, or ...)
in a bare $arch-elf target.
Ok?
2016-03-25 Doug Evans <dje@google.com>
* configure.tgt (x86_64-*-elf*): Remove i386bsd-tdep.o.
diff --git a/gdb/configure.tgt b/gdb/configure.tgt
index c2b9c40..62c2331 100644
--- a/gdb/configure.tgt
+++ b/gdb/configure.tgt
@@ -650,9 +650,9 @@ x86_64-*-dicos*)
gdb_target_obs="amd64-tdep.o i386-tdep.o i387-tdep.o \
dicos-tdep.o i386-dicos-tdep.o amd64-dicos-tdep.o"
;;
-x86_64-*-elf* | x86_64-*-rtems*)
- gdb_target_obs="amd64-tdep.o i386-tdep.o i387-tdep.o i386bsd-tdep.o"
- ;;
+x86_64-*-elf*)
+ gdb_target_obs="amd64-tdep.o i386-tdep.o i387-tdep.o"
+ ;;
x86_64-*-linux*)
# Target: GNU/Linux x86-64
gdb_target_obs="amd64-tdep.o amd64-linux-tdep.o i386-tdep.o \
@@ -684,6 +684,9 @@ x86_64-*-openbsd*)
i387-tdep.o i386bsd-tdep.o i386obsd-tdep.o \
obsd-tdep.o bsd-uthread.o solib-svr4.o"
;;
+x86_64-*-rtems*)
+ gdb_target_obs="amd64-tdep.o i386-tdep.o i387-tdep.o i386bsd-tdep.o"
+ ;;
xtensa*-*-linux*) gdb_target=linux
# Target: GNU/Linux Xtensa
gdb_target_obs="xtensa-tdep.o xtensa-config.o xtensa-linux-tdep.o \
next reply other threads:[~2016-03-25 16:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-25 16:30 Doug Evans [this message]
2016-03-29 17:41 ` Pedro Alves
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=94eb2c0bbbf28763bf052ee215f4@google.com \
--to=dje@google.com \
--cc=gdb-patches@sourceware.org \
--cc=joel.sherrill@oarcorp.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).