public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/99918] [9/10/11 Regression] suboptimal code for bool bitfield tests
Date: Mon, 05 Apr 2021 20:40:38 +0000	[thread overview]
Message-ID: <bug-99918-4-GbsXRfbwsF@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-99918-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #4 from Martin Sebor <msebor at gcc dot gnu.org> ---
(In reply to Andrew Pinski from comment #1)
> This comes down to lowering bitfields too soon.
> my bet it will happen even integer bitfields will have a problem.

Yes, unsigned bit-fields suffer the same problem but unlike for _Bool, GCC
never emitted optimal code for those for this test case.

  parent reply	other threads:[~2021-04-05 20:40 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-05 20:15 [Bug tree-optimization/99918] New: " msebor at gcc dot gnu.org
2021-04-05 20:22 ` [Bug tree-optimization/99918] " pinskia at gcc dot gnu.org
2021-04-05 20:23 ` [Bug tree-optimization/99918] [9/10/11 Regression] " msebor at gcc dot gnu.org
2021-04-05 20:27 ` msebor at gcc dot gnu.org
2021-04-05 20:40 ` msebor at gcc dot gnu.org [this message]
2021-04-06  8:39 ` rguenth at gcc dot gnu.org
2021-04-08 14:22 ` rguenth at gcc dot gnu.org
2021-06-01  8:20 ` [Bug tree-optimization/99918] [9/10/11/12 " rguenth at gcc dot gnu.org
2022-05-27  9:44 ` [Bug tree-optimization/99918] [10/11/12/13 " rguenth at gcc dot gnu.org
2022-06-28 10:44 ` jakub at gcc dot gnu.org
2022-07-01 12:49 ` fkorta at gmail dot com
2023-07-07 10:39 ` [Bug tree-optimization/99918] [11/12/13/14 " rguenth at gcc dot gnu.org
2023-07-12 22:05 ` 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-99918-4-GbsXRfbwsF@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).