public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/97223] Failure to optimize comparison of char arithmetic to single comparison
Date: Mon, 28 Sep 2020 07:33:36 +0000	[thread overview]
Message-ID: <bug-97223-4-KOrOnwviGS@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-97223-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97223

Richard Biener <rguenth at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
     Ever confirmed|0                           |1
   Last reconfirmed|                            |2020-09-28
             Status|UNCONFIRMED                 |NEW
           Keywords|                            |easyhack

--- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> ---
It works for 'unsigned char' but not for signed char (or signed short) which
are promoted to 'int' and then shortened to unsigned arithmetic:

return <retval> = (short int) ((unsigned short) x + 5) > x;

there's existing patterns that would need to be amended for the extra
conversion.

  reply	other threads:[~2020-09-28  7:33 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-28  7:14 [Bug tree-optimization/97223] New: Failure to optimize comparison of char arithmetic to comparison gabravier at gmail dot com
2020-09-28  7:33 ` rguenth at gcc dot gnu.org [this message]
2020-10-31  5:18 ` [Bug tree-optimization/97223] Failure to optimize comparison of char arithmetic to single comparison erozen at microsoft dot com
2020-11-07  1:54 ` erozen at microsoft dot com
2021-01-14 21:13 ` erozen at microsoft dot com
2021-08-24 19:38 ` arjun.is at lostca dot se

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=bug-97223-4-KOrOnwviGS@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.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).