Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: David Ung <davidu@mips.com>
To: Andrew Cagney <cagney@gnu.org>
Cc: cgd@broadcom.com, gdb-patches@sources.redhat.com, nigel@mips.com
Subject: Re: MIPS32 / MIPS64 release 2 support in simulator
Date: Mon, 08 Nov 2004 18:06:00 -0000	[thread overview]
Message-ID: <1099937194.2780.151.camel@stockwell.mips.com> (raw)
In-Reply-To: <418FA243.4060507@gnu.org>

On Mon, 2004-11-08 at 16:43, Andrew Cagney wrote:
> cgd@broadcom.com wrote:
> > At Thu, 4 Nov 2004 13:53:38 +0000 (UTC), "David Ung" wrote:
> > 
> >>I shall update mips.igen with the new r2 instructions and then submit it
> >>as a patch.
> > 
> > 
> > cool, thanks.
> 
> Don't.  These new changes go in a new file, and that file gets a very 
> clear FSF copyright.
> 
> Andrew
> 

arhh.  Chris's argument of that the rest of the tools consider rev 2
instructions as an ISA is quite a valid one.  And for consistency with
the existing structure, it looks to be the right thing to do.  
But when I got to merging in the r2 instructions into mips.igen, I do
see that for every mips32 / 64 instruction, I now have to also tag them
mips32r2 / 64r2.  It would probably be nicer to just tell it to include
all the mips32 instructions (which would be like treating it as an
ASE).  
But then again it brings us back to the original argument, and I
probably would lean slightly towards the ISA model and be part of
mips.igen depite polluting the whole file with *mips32r2: and *mips64r2:
tags.

David.


  reply	other threads:[~2004-11-08 18:06 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 [this message]
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
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=1099937194.2780.151.camel@stockwell.mips.com \
    --to=davidu@mips.com \
    --cc=cagney@gnu.org \
    --cc=cgd@broadcom.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