Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andrew Cagney <cagney@gnu.org>
To: cgd@broadcom.com
Cc: David Ung <davidu@mips.com>,
	gdb-patches@sources.redhat.com, nigel@mips.com
Subject: Re: MIPS32 / MIPS64 release 2 support in simulator
Date: Tue, 09 Nov 2004 17:00:00 -0000	[thread overview]
Message-ID: <4190F770.70006@gnu.org> (raw)
In-Reply-To: <yov5vfcff0v6.fsf@xl-sj1-04.sj.broadcom.com>

cgd@broadcom.com wrote:
> At Tue, 09 Nov 2004 11:10:40 -0500, Andrew Cagney wrote:
> 
>>David, this isn't a technical decision (if it were, Chris would be
>>right).  The new changes, or more exactly the new instructions, go in
>>a new file clearly marked (C) FSF (and for that matter clearly stating
>>that it was contributed by MIPS Inc).  As for the mark-up of the
>>existing instructions, that's mindnumming tedium.
>>
>>Sorry about this pedentary.  I'm off to pester another lawyer.
> 
> 
> Andrew,
> 
> Once the legal issues are resolved on your end, will be it be
> acceptable from your POV to merge them all into mips.igen?
> 
> Or do you believe they should always be separate?

That's a technical question, as I shouldn't, I don't care!

> (Why is this necessary now, when it wasn't necessary back when we
> contributed the original mips32/mips64 support?)

That was a screw-up on my part.  You'll see I more recently integrated 
the altivec instructions into the PPC as a separate file.

Andrew


  reply	other threads:[~2004-11-09 17:00 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-03 15:26 David Ung
     [not found] ` <mailpost.1099495587.2562@news-sj1-1>
2004-11-03 16:54   ` cgd
2004-11-03 16:57   ` cgd
     [not found]     ` <mailpost.1099501062.5136@news-sj1-1>
2004-11-03 19:01       ` cgd
2004-11-04 13:53         ` David Ung
     [not found]           ` <mailpost.1099576418.9773@news-sj1-1>
2004-11-04 17:46             ` cgd
2004-11-08 16:44               ` Andrew Cagney
2004-11-08 18:06                 ` David Ung
2004-11-09 15:54                   ` David Ung
2004-11-09 16:12                   ` Andrew Cagney
2004-11-09 16:23                     ` cgd
2004-11-09 17:00                       ` Andrew Cagney [this message]
2004-11-09 17:38                         ` cgd
2004-11-24 17:08                           ` David Ung
2004-11-24 18:17                             ` cgd
2005-05-18 18:11                               ` [patch ping] " David Ung
2005-05-19  2:04                                 ` cgd
     [not found]                                   ` <mailpost.1116450142.2303@news-sj1-1>
2005-05-25  2:21                                     ` cgd
2005-05-26 22:27                                       ` cgd
2005-05-27 14:38                                         ` David Ung
2004-11-09 23:36                         ` Nigel Stephens

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=4190F770.70006@gnu.org \
    --to=cagney@gnu.org \
    --cc=cgd@broadcom.com \
    --cc=davidu@mips.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=nigel@mips.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