From: Lev Yudalevich <lyudalev@gmail.com>
To: cgen@sourceware.org
Subject: Unusual architecture support?
Date: Sun, 26 Feb 2012 14:49:00 -0000 [thread overview]
Message-ID: <CA+zUDe3rY8V2n4jWWGvDaURE=KPY48KF4grBB-6CcES2hYQeyw@mail.gmail.com> (raw)
In-Reply-To: <CA+zUDe33OJTChBXXDT59oBJFTc-zcfDpOjN36NevNbDPq=WrEw@mail.gmail.com>
Hi,
I have to implement a development tool chain (assembler, linker etc)
for a custom controller with a very special architecture. It has
several memory areas and several instruction pointers to them. Each
instruction should be spited in such a way that one piece of the
instruction goes to one memory section and another piece of the
instruction goes into another section. I’m wondering whether CGEN can
provide a framework for such an unusual architecture. Any ideas are
highly appreciated.
Sincerely,
Lev.
parent reply other threads:[~2012-02-26 14:49 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <CA+zUDe33OJTChBXXDT59oBJFTc-zcfDpOjN36NevNbDPq=WrEw@mail.gmail.com>]
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='CA+zUDe3rY8V2n4jWWGvDaURE=KPY48KF4grBB-6CcES2hYQeyw@mail.gmail.com' \
--to=lyudalev@gmail.com \
--cc=cgen@sourceware.org \
/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).