From: Andreas Schwab <schwab@linux-m68k.org>
To: Paul Koning via Gcc <gcc@gcc.gnu.org>
Cc: Paul Koning <paulkoning@comcast.net>
Subject: Re: Signed vs. unsigned compares
Date: Fri, 17 Jun 2022 17:51:19 +0200 [thread overview]
Message-ID: <8735g3s2yw.fsf@igel.home> (raw)
In-Reply-To: <F5AC5383-A9F9-4A39-A929-521F4F403EA7@comcast.net> (Paul Koning via Gcc's message of "Fri, 17 Jun 2022 11:32:52 -0400")
On Jun 17 2022, Paul Koning via Gcc wrote:
> In expanding a longer-than-word compare, I need to do things differently depending on whether a signed vs. unsigned compare is needed. But it seems the compare operation applies to either. How can I do this in the target code?
There are both signed and unsigned comparison operations, eg. GE
vs. GEU.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC1
"And now for something completely different."
next prev parent reply other threads:[~2022-06-17 15:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-17 15:32 Paul Koning
2022-06-17 15:51 ` Andreas Schwab [this message]
2022-06-17 16:52 ` Paul Koning
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=8735g3s2yw.fsf@igel.home \
--to=schwab@linux-m68k.org \
--cc=gcc@gcc.gnu.org \
--cc=paulkoning@comcast.net \
/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).