From: Peter Barada <pbarada@mail.wm.sps.mot.com>
To: ac131313@cygnus.com
Cc: Peter.Barada@motorola.com, gdb@sources.redhat.com
Subject: Re: support for different sized FPU registers
Date: Mon, 03 Jun 2002 07:06:00 -0000 [thread overview]
Message-ID: <200206031406.g53E68Z09344@hyper.wm.sps.mot.com> (raw)
In-Reply-To: <3CF94BAE.7000506@cygnus.com> (message from Andrew Cagney on Sat, 01 Jun 2002 18:33:18 -0400)
>The most immediate thing that is needed is for the m68k family to be
>up-dated to the new multi-arch framework. Once that is done, handling
>both a coldfire and an m68k is fairly mechanical. Check other targets
>such as PPC, xstormy16, mn10300 et.al. for examples.
I've hacked together a 'set m68kfpu' command to switch the fpu length,
and that seems to work for me.
Is there a document anywhere that has a 'recipe' for converting a old
back-end into a new and improved multi-arched framework?
>Do you have an FSF assignment in place?
I'm working on convincing the lawyers that the FSF assignment is a
good thing(tm)....
--
Peter Barada Peter.Barada@motorola.com
Wizard 781-852-2768 (direct)
WaveMark Solutions(wholly owned by Motorola) 781-270-0193 (fax)
prev parent reply other threads:[~2002-06-03 14:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-29 15:17 Peter Barada
2002-06-01 15:33 ` Andrew Cagney
2002-06-03 7:06 ` Peter Barada [this message]
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=200206031406.g53E68Z09344@hyper.wm.sps.mot.com \
--to=pbarada@mail.wm.sps.mot.com \
--cc=Peter.Barada@motorola.com \
--cc=ac131313@cygnus.com \
--cc=gdb@sources.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