Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andrew Cagney <cagney@gnu.org>
To: Daniel Jacobowitz <drow@false.org>
Cc: Mark Kettenis <kettenis@gnu.org>, gdb-patches@sources.redhat.com
Subject: Re: [COMMIT] OpenBSD/mips64 target and native support
Date: Mon, 25 Oct 2004 19:01:00 -0000	[thread overview]
Message-ID: <417D4D56.80003@gnu.org> (raw)
In-Reply-To: <20041025152912.GA28110@nevyn.them.org>

Daniel Jacobowitz wrote:
> On Mon, Oct 25, 2004 at 11:23:21AM -0400, Andrew Cagney wrote:
> 
>>Mark Kettenis wrote:
>>
>>>This seems to be working pretty reasonably, so I checked it in.  I
>>>suppose not many people are running OpenBSD/mips64 (OpenBSD/sgi) yet,
>>>but those that do, probably want a working debugger.
>>>
>>>Anyway, I'm not adding a NEWS entry yet, since there are some issues
>>>with dwarf2read.c that need to be resolved before the native stuff
>>>really works.
>>
>>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.

Andrew


  reply	other threads:[~2004-10-25 19:01 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 [this message]
2004-10-31 18:39       ` Andrew Cagney
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=417D4D56.80003@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