public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "goon.pri.low at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/112659] missed-optimization: if (exp) return exp; else return 0;
Date: Tue, 21 Nov 2023 22:19:59 +0000	[thread overview]
Message-ID: <bug-112659-4-8QqC2kpTn1@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-112659-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #4 from gooncreeper <goon.pri.low at gmail dot com> ---
(In reply to Andrew Pinski from comment #2)
> >Note: this happens for all operators, not just addition!
> 
> Actually it is just addition with a constant on the trunk.
> ```
> int g(int v, int b) {
>     if (v - b)
>         return v - b ;
>     else
>         return 0;
> }
> ```
> was handled with PR 19832.
> 
> 
> I see division with a constant is not handled though:
> ```
> int unopt(int v, int b) {
>     if (v /2)
>         return v / 2;
>     else
>         return 0;
> }
> ```


I am not quite testing on the trunk build but I also believe modulo

  parent reply	other threads:[~2023-11-21 22:19 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-21 21:56 [Bug tree-optimization/112659] New: " goon.pri.low at gmail dot com
2023-11-21 22:05 ` [Bug tree-optimization/112659] " pinskia at gcc dot gnu.org
2023-11-21 22:14 ` pinskia at gcc dot gnu.org
2023-11-21 22:16 ` pinskia at gcc dot gnu.org
2023-11-21 22:19 ` goon.pri.low at gmail dot com [this message]
2023-11-21 22:29 ` pinskia at gcc dot gnu.org
2024-05-08  7:43 ` pinskia at gcc dot gnu.org
2024-05-08  7:47 ` pinskia at gcc dot gnu.org
2024-05-08 23:35 ` pinskia at gcc dot gnu.org
2024-05-09 18:11 ` pinskia at gcc dot gnu.org

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-112659-4-8QqC2kpTn1@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).