public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Richard Henderson <rth@redhat.com>
To: "Paulo J. Matos" <pocmatos@gmail.com>
Cc: gcc@gcc.gnu.org
Subject: Re: splitting add instructions
Date: Tue, 19 Jul 2011 15:42:00 -0000	[thread overview]
Message-ID: <4E25A5C5.8020606@redhat.com> (raw)
In-Reply-To: <j03gde$gba$1@dough.gmane.org>

On 07/19/2011 01:48 AM, Paulo J. Matos wrote:
> I have been looking at the rx port. Seems to be very similar to mine
> in that it has an add and adc where both set the flags and no
> explicit hard register for cc. Mine is actually simpler in that there
> is only CCmode since we don't have floating point operations in the
> chip. Will use rx as a guide! :)

Note that while RX has one mode for floating-point, it has
two other modes to deal with instructions that fail to set
all of the flags (or fails to set the flags in a way that
is useful for the comparison).

Depending on how regular your instructions are, you may
find that CCmode is not enough to eliminate all comparisons.
It is, however, a good start.


r~

  reply	other threads:[~2011-07-19 15:42 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-18 16:49 Paulo J. Matos
2011-07-18 16:59 ` Richard Henderson
2011-07-18 17:31   ` Paul Koning
2011-07-18 21:20     ` Richard Henderson
2011-07-19  8:27       ` Paulo J. Matos
2011-07-19 10:21         ` Paulo J. Matos
2011-07-19 15:42           ` Richard Henderson [this message]
2011-07-19 15:58             ` Paulo J. Matos
2011-07-19 16:08             ` Paulo J. Matos
2011-07-19 16:43               ` Richard Henderson
2011-07-19 12:57         ` Paul Koning
2011-07-19  8:30   ` Paulo J. Matos
2011-07-19 10:30   ` Paulo J. Matos
2011-07-19 10:52     ` Paulo J. Matos
2011-07-19 15:06   ` Paulo J. Matos
2011-07-19 15:09     ` DJ Delorie
2011-07-19 15:21       ` Paulo J. Matos
2011-07-19 15:42         ` Richard Henderson
2011-07-19 15:42           ` Paulo J. Matos
2011-07-18 17:29 ` Ian Lance Taylor
2011-07-19  8:49   ` Paulo J. Matos

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=4E25A5C5.8020606@redhat.com \
    --to=rth@redhat.com \
    --cc=gcc@gcc.gnu.org \
    --cc=pocmatos@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).