From: Andrew Cagney <cagney@gnu.org>
To: Daniel Jacobowitz <drow@false.org>, Mark Kettenis <kettenis@gnu.org>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [COMMIT] OpenBSD/mips64 target and native support
Date: Sun, 31 Oct 2004 18:39:00 -0000 [thread overview]
Message-ID: <4185314C.7020307@gnu.org> (raw)
In-Reply-To: <417D4D56.80003@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 878 bytes --]
>>> This part:
>>>
>>>
>>>> +DEPRECATED_TM_FILE= tm-nbsd.h
>>>
>>>
>>> is no longer acceptable.
>>
>>
>>
>> Do you have an alternate suggestion?
>>
>> It seems pretty strange to me to forbid new OS ports of MIPS targets
>> just because every single MIPS target including the core MIPS support
>> still uses DEPRECATED_TM_FILE.
>
>
> I'm lost, what has this to do with the MIPS? When adding any new native
> or target, DEPRECATED_TM_FILE is not acceptable.
The situtation we have here is identical to that we encountered when we
first made it a requirement that not just new architectures, but also
extensions to exsting architectures, had to be multi-arch. We set the
standard and then helped developers exceed it.
Our only mistake was to "blink" when it came to the solib problem.
We've been "blinking" for too many years now.
I've committed the attached,
Andrew
[-- Attachment #2: diffs --]
[-- Type: text/plain, Size: 556 bytes --]
2004-10-31 Andrew Cagney <cagney@gnu.org>
* config/mips/obsd64.mt (DEPRECATED_TM_FILE): Delete.
Index: config/mips/obsd64.mt
===================================================================
RCS file: /cvs/src/src/gdb/config/mips/obsd64.mt,v
retrieving revision 1.1
diff -p -u -r1.1 obsd64.mt
--- config/mips/obsd64.mt 23 Oct 2004 12:14:02 -0000 1.1
+++ config/mips/obsd64.mt 31 Oct 2004 18:21:28 -0000
@@ -1,3 +1,2 @@
# Target: OpenBSD/mips64
TDEPFILES= mips-tdep.o mips64obsd-tdep.o corelow.o solib.o solib-svr4.o
-DEPRECATED_TM_FILE= tm-nbsd.h
next prev parent reply other threads:[~2004-10-31 18:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-23 12:16 Mark Kettenis
2004-10-25 15:24 ` Andrew Cagney
2004-10-25 15:29 ` Daniel Jacobowitz
2004-10-25 19:01 ` Andrew Cagney
2004-10-31 18:39 ` Andrew Cagney [this message]
2004-10-31 19:45 ` Mark Kettenis
2004-10-31 20:07 ` Andrew Cagney
2004-10-31 22:28 ` Mark Kettenis
2004-11-01 0:48 ` Andrew Cagney
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=4185314C.7020307@gnu.org \
--to=cagney@gnu.org \
--cc=drow@false.org \
--cc=gdb-patches@sources.redhat.com \
--cc=kettenis@gnu.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