From: "Frank Ch. Eigler" <fche@redhat.com>
To: Joern Rennecke <joernr@arc.com>
Cc: cgen@sources.redhat.com
Subject: Re: copyright issues for cgen-generated tools
Date: Tue, 16 Jan 2007 19:29:00 -0000 [thread overview]
Message-ID: <20070116192918.GA1841@redhat.com> (raw)
In-Reply-To: <20070116132856.GA27599@elsdt-razorfish.arc.com>
Hi -
On Tue, Jan 16, 2007 at 01:28:56PM +0000, Joern Rennecke wrote:
> [...]
> The features I hoped to re-use from the sh port cpu are variable length
> instruction parsing for a bi-endian cpu that is actually (insn-lsb0? #t),
> and delay slot handling for the simulators. [...]
Go ahead.
> Also, worrying about m32r.cpu is that it has ChangeLog entries that
> are newer than the Copyright notices. [...]
I'm sure that's just sloppy copyright date updating.
> [...]
> I'm thinking of using something like the code below; does that make sense?
> [...]
> (dnmf f-rel21 "21 bit pc relative signed offset" (PCREL-ADDR) INT
> (f-d21l f-d21h)
> (sequence () ; insert
> (set (ifield f-d21l)
> (and (srl (sub (ifield f-rel21) (and pc (const -4)))
> (const 1))
> (const #x3ff)))
> (set (ifield f-d21h)
> (sra (sub (ifield f-rel21) (and pc (const -4)))
> (const 11)))
> )
> [...]
Yes, if the "current pc" were thusly available. I believe however
that it is not, and that this will likely require hand-crafted
assembler operand parsers / relocations, and all that good stuff.
For an older Cygnus-authored target port, we built something called
"complex relocations", which can be used to automatically encode
complex link-time expressions into assembly operands. IIRC this part
is being prepared for contribution to the FSF code base, but this is
bound to be a controversial addition.
- FChE
prev parent reply other threads:[~2007-01-16 19:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-15 11:38 Joern Rennecke
2007-01-15 19:39 ` Frank Ch. Eigler
2007-01-16 13:31 ` Joern Rennecke
2007-01-16 15:01 ` Dave Brolley
2007-01-16 19:29 ` Frank Ch. Eigler [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=20070116192918.GA1841@redhat.com \
--to=fche@redhat.com \
--cc=cgen@sources.redhat.com \
--cc=joernr@arc.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).