public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jim Wilson <wilson@specifixinc.com>
To: Feranando Roberto Secco <secco@inf.ufsc.br>
Cc: gcc@gcc.gnu.org
Subject: Re: machine files from 2.95 to 3.2.3
Date: Tue, 30 Mar 2004 05:59:00 -0000	[thread overview]
Message-ID: <4068C5F2.2060200@specifixinc.com> (raw)
In-Reply-To: <405F6245.8090705@inf.ufsc.br>

Feranando Roberto Secco wrote:
> What do I have to change in the target files  in order to
> make the 2.95 files compatible with 3.2.3 files?
> Is it possible are they compatible?

It is very unlikely that they will work as is.  You will have to change 
some stuff.  We don't maintain lists of what needs to change.  Most of 
the stuff should be obvious, e.g. you define a macro that is now 
poisoned, and you have to change the port to use the new macro that 
replaced the poisoned one.  Most of the trouble is likely to be with the 
target .h file.  There should be little in the md file that needs to be 
changed.

There may be style issues that you miss with a naive port, since 
sometimes there are multiple ways to solve a problem, with the old ones 
obsoleted but not yet removed.  For instance, there is now a way to 
define constants in the md file, and style dictates use of this.  There 
is a new mechanism for describing hardware pipelines which is better 
than the old one, but the old one is still present and still works.  Etc.
-- 
Jim Wilson, GNU Tools Support, http://www.SpecifixInc.com

      reply	other threads:[~2004-03-30  0:57 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-23  7:38 Feranando Roberto Secco
2004-03-30  5:59 ` Jim Wilson [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=4068C5F2.2060200@specifixinc.com \
    --to=wilson@specifixinc.com \
    --cc=gcc@gcc.gnu.org \
    --cc=secco@inf.ufsc.br \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).