public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/64450] Optimize 0>=p-q to q>=p for char*p,*q; Date: Sun, 14 May 2023 23:20:11 +0000 [thread overview] Message-ID: <bug-64450-4-tIWxzqQhAD@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-64450-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64450 --- Comment #3 from Andrew Pinski <pinskia at gcc dot gnu.org> --- (for cmp (tcc_comparison) (simplify (cmp (pointer_diff @0 @1) integer_zero_p) (cmp @0 @1))) Maybe .... But we might also need handle the match patterns for too: A CMP B ? A - B : -(A - B) A CMP B ? A - B : B - A (which is also on my todo list anyways).
next prev parent reply other threads:[~2023-05-14 23:20 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-12-30 20:58 [Bug c++/64450] New: " gcc-bugzilla at contacts dot eelis.net 2014-12-30 20:59 ` [Bug c++/64450] " ville.voutilainen at gmail dot com 2014-12-30 21:36 ` [Bug tree-optimization/64450] " glisse at gcc dot gnu.org 2014-12-30 21:38 ` pinskia at gcc dot gnu.org 2023-05-14 23:20 ` pinskia at gcc dot gnu.org [this message] 2023-10-23 15:20 ` 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-64450-4-tIWxzqQhAD@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: linkBe 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).