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/67628] [tree-optimization] (a && b) && c shows better codegen than a && (b && c)
Date: Mon, 07 Jun 2021 07:30:03 +0000	[thread overview]
Message-ID: <bug-67628-4-OMbp5701xt@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-67628-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #6 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
Another testcase which shows the problem to be even worse:
#define isgap(c) ((c) == ' ' || (c) == '.' || (c) == '_' || (c) == '-' || (c)
== '~')

int f(char a)
{
  return isgap(a);
}

  parent reply	other threads:[~2021-06-07  7:30 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-18 14:32 [Bug tree-optimization/67628] New: " ktkachov at gcc dot gnu.org
2015-09-18 14:48 ` [Bug tree-optimization/67628] " pinskia at gcc dot gnu.org
2015-09-18 15:00 ` ktkachov at gcc dot gnu.org
2015-09-18 15:10 ` pinskia at gcc dot gnu.org
2015-09-21 14:23 ` ktkachov at gcc dot gnu.org
2021-06-07  7:30 ` pinskia at gcc dot gnu.org [this message]
2021-07-20  6:50 ` pinskia at gcc dot gnu.org
2023-09-03  3:29 ` 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-67628-4-OMbp5701xt@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).