From: Joern Rennecke <joern.rennecke@embecosm.com>
To: Doug Evans <dje@sebabeach.org>
Cc: cgen@sourceware.org
Subject: Re: ALIAS instructions are messed up?
Date: Sat, 03 Oct 2009 20:33:00 -0000 [thread overview]
Message-ID: <20091003163955.51so5zjyysow04k8-nzlynne@webmail.spamcop.net> (raw)
> Whether to disallow alias insns entirely is a separate question. Dunno.
> [We could still keep it for macro-insns.
> And I realize there are a few ports that currently use it, or at
> least specify > it.]
Currently, macro-instructions can't be used in all instances where
it should be natural to use them.
When you want to set a multi-ifield to a constant, you end up with
the entire costant being added in in the bit position of each of
constituent simple bitfields.
By adding an ALIAS instruction by hand, you can at least work around
the problem by setting only simple bitfields to constants.
next reply other threads:[~2009-10-03 20:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-03 20:33 Joern Rennecke [this message]
2009-10-05 18:22 ` Doug Evans
2009-10-05 21:42 ` Joern Rennecke
-- strict thread matches above, loose matches on Subject: below --
2009-06-18 17:27 Doug Evans
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=20091003163955.51so5zjyysow04k8-nzlynne@webmail.spamcop.net \
--to=joern.rennecke@embecosm.com \
--cc=cgen@sourceware.org \
--cc=dje@sebabeach.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).