Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: jtc@redback.com (J.T. Conklin)
To: Will Cohen <wcohen@redhat.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: Patch to provide m68k simulator to gdb
Date: Tue, 27 Feb 2001 15:35:00 -0000	[thread overview]
Message-ID: <5my9uru2c4.fsf@jtc.redback.com> (raw)
In-Reply-To: <3A9C3128.A52307A@redhat.com>

>>>>> "Will" == Will Cohen <wcohen@redhat.com> writes:
Will> DJ Delorie and I have integrated the m68k emulator from the Un*x
Will> Amiga Emulator (UAE) with gdb. UAE is GPL'ed software. The
Will> ChangeLog entries and patch file are attached to this mail.  I
Will> would like to get this incorporated into gdb. Other people
Will> might find this patch useful.

Cool.  I've wanted a simulator for the m68k family for some time.

Some issues:

  * You say that UAE is GPL'd (and the UAE webpage also states this),
    but there is nothing in the source files that indicate this.  The
    files have the copyright statements of individual persons with no
    redistribution or licencing info.  I personally am very hesitant 
    to integrate such code as is.

  * I see from the UAE webpage, that the simulator can emulate a '000,
    '010, or '020.  For GDB, we'd want to add support for the '040 and
    '060; and perhaps the ColdFire.  While the onus is on us to add such
    features, do we have anything in place to keep divergence between 
    the two codebases to a minimum.  

  * I haven't looked at the FPU emulator, but if it doesn't do software
    FP, we'll have to re-implement it otherwise 96bit extended doubles
    won't work as expected.

  * The defines in sim/m68k/target.h don't seem to be used.  In fact,
    there appears to be quite a bit of code that isn't used.  This 
    could be cleaned up, but it won't be worth doing so unless our
    changes can be integrated into the master UAE sources (or we 
    decide to branch).


        --jtc

-- 
J.T. Conklin
RedBack Networks


  reply	other threads:[~2001-02-27 15:35 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-02-27 14:59 Will Cohen
2001-02-27 15:35 ` J.T. Conklin [this message]
2001-02-28  8:02   ` Andrew Cagney
2001-02-28  8:58     ` Will Cohen
2001-02-28  9:17       ` Andrew Cagney
2001-03-05 13:12         ` Will Cohen
2001-02-28  8:39 ` Andrew Cagney
2001-02-28  9:01   ` Will Cohen
2001-03-01 11:24   ` Will Cohen
2001-03-01 11:54     ` Andrew Cagney
2001-03-05 13:25   ` Will Cohen
2001-03-05 14:57     ` Andrew Cagney
2001-03-06  8:22       ` Will Cohen
2001-03-06 10:07         ` Frank Ch. Eigler
2001-03-09 12:54           ` Andrew Cagney
2001-03-05 15:12     ` Andrew Cagney
2001-03-06 10:11       ` Frank Ch. Eigler

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=5my9uru2c4.fsf@jtc.redback.com \
    --to=jtc@redback.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=wcohen@redhat.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