From: Dave Brolley <brolley@redhat.com>
To: Venkataramanan Kumar <itsvenkat31@gmail.com>
Cc: cgen@sourceware.org
Subject: Re: Porting Binutils
Date: Tue, 13 Jan 2009 16:29:00 -0000 [thread overview]
Message-ID: <496CC140.2020006@redhat.com> (raw)
In-Reply-To: <d70a7cd60901070208h64947866ld3f033679bf3bcbb@mail.gmail.com>
Hi,
Generally one starts by cloning an existing port which is similar to the
new one. I usually do this by copying all of the files and directories
named after the port to be cloned and by grepping the remaining
source/Makefiles/scripts for references to the old port and copying them
to add the new port. This leaves you with a new port which behaves like
the old one. I then start ripping out the details of the old port and
replacing them with implementation of the new one.
There is some documentation in cgen/doc which may also be helpful for
learning the scheme-like cgen .cpu language and how to generate source
from the .cpu and .opc files for your port.
I hope this helps,
Dave
Venkataramanan Kumar wrote:
> Hi,
>
> I am working on porting GCC and binutils to a target similar to MIPS.
> I have completed basic compiler port.
> Now I need to port binutils. Can you please give a brief introduction
> on how to start using CGEN.
>
> Thank is advance.
>
prev parent reply other threads:[~2009-01-13 16:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-07 10:08 Venkataramanan Kumar
2009-01-13 16:29 ` Dave Brolley [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=496CC140.2020006@redhat.com \
--to=brolley@redhat.com \
--cc=cgen@sourceware.org \
--cc=itsvenkat31@gmail.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).