From: Hans-Peter Nilsson <hp@bitrange.com>
To: DJ Delorie <dj@redhat.com>
Cc: tnt@246tNt.com, gcc@gcc.gnu.org
Subject: Re: Design a microcontroller for gcc
Date: Thu, 16 Feb 2006 03:56:00 -0000 [thread overview]
Message-ID: <Pine.BSF.4.58.0602152243560.43519@dair.pair.com> (raw)
In-Reply-To: <200602160340.k1G3e9ss000475@greed.delorie.com>
On Wed, 15 Feb 2006, DJ Delorie wrote:
> I hope I can stick with my cmp/jmp model and manage them myself still,
> though, because there's a LOT of patterns in m32c where the set of
> flags affected depends on which alternative you select, and most
> patterns affect the flags in some (usually nonorthagonal) way.
Unless I'm delirious (it's way past bedtime) I see a m32c port
and it's cc0-free. Is there a problem?
> Or is gcc going to start putting things between the cmp and jmp?
Yes. At least reload wants to do that. The choice a port has
is to either have cc-free reload insns (like i386) or keep the
cc setter and user combined at least until after reload
(cbranch, but you don't have to use the cbranchM4 name; you can
do the combination to a cbranch-type insn in the CC user).
Not my idea, so it's probably sane. :-)
brgds, H-P
PS. There may be other choices, but none that caught my attention.
next prev parent reply other threads:[~2006-02-16 3:56 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-14 23:22 Sylvain Munaut
2006-02-14 23:40 ` DJ Delorie
2006-02-15 0:28 ` Sylvain Munaut
2006-02-15 0:41 ` DJ Delorie
2006-02-15 19:59 ` Sylvain Munaut
2006-02-15 20:06 ` DJ Delorie
2006-02-15 20:23 ` Paul Brook
2006-02-15 21:21 ` DJ Delorie
2006-02-15 22:10 ` Hans-Peter Nilsson
2006-02-15 23:10 ` David Daney
2006-02-16 0:26 ` Sylvain Munaut
2006-02-16 0:46 ` DJ Delorie
2006-02-16 2:49 ` Hans-Peter Nilsson
2006-02-16 3:21 ` DJ Delorie
2006-02-16 3:34 ` Hans-Peter Nilsson
2006-02-16 3:37 ` Hans-Peter Nilsson
2006-02-16 3:44 ` DJ Delorie
2006-02-16 3:40 ` DJ Delorie
2006-02-16 3:56 ` Hans-Peter Nilsson [this message]
2006-02-16 4:10 ` Hans-Peter Nilsson
2006-02-16 4:17 ` DJ Delorie
2006-02-16 4:13 ` DJ Delorie
2006-02-16 11:42 ` Hans-Peter Nilsson
2006-02-16 20:49 ` Sylvain Munaut
2006-02-17 0:28 ` Hans-Peter Nilsson
2006-02-20 8:54 ` Sylvain Munaut
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=Pine.BSF.4.58.0602152243560.43519@dair.pair.com \
--to=hp@bitrange.com \
--cc=dj@redhat.com \
--cc=gcc@gcc.gnu.org \
--cc=tnt@246tNt.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).