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/99919] [11/12/13/14 Regression] bogus -Wmaybe-uninitialized with a _Bool bit-field Date: Fri, 15 Dec 2023 13:33:56 +0000 [thread overview] Message-ID: <bug-99919-4-4Vz2kolDh3@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-99919-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99919 Richard Biener <rguenth at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Last reconfirmed|2021-11-30 00:00:00 |2023-12-15 CC| |jamborm at gcc dot gnu.org --- Comment #10 from Richard Biener <rguenth at gcc dot gnu.org> --- This is also a missed SRA optimization. SRA produces b$i_16 = b.i; b$j_17 = b.j; b.i = b$i_16; b.j = b$j_17; _1 = VIEW_CONVERT_EXPR<unsigned char>(b); _2 = _1 & 1; ... b.i = b$i_16; b.j = b$j_15; _4 = VIEW_CONVERT_EXPR<unsigned char>(b); _5 = _4 & 2; which is sub-optimal - for some reason it chooses to create replacements for i and j instead of a unsigned char replacement for the whole aggregate driven by the V_C_E access access { base = (2771)'b', offset = 0, size = 8, expr = b, type = struct B, reverse = 0, grp_read = 1, grp_write = 0, grp_assignment_read = 1, grp_assignment_write = 0, grp_scalar_read = 0, grp_scalar_write = 0, grp_total_scalarization = 0, grp_hint = 0, grp_covered = 0, grp_unscalarizable_region = 0, grp_unscalarized_data = 1, grp_same_access_path = 1, grp_partial_lhs = 0, grp_to_be_replaced = 0, grp_to_be_debug_replaced = 0} is also odd because the access type is really 'unsigned char'? That seems to be because /* We need to dive through V_C_Es in order to get the size of its parameter and not the result type. Ada produces such statements. We are also capable of handling the topmost V_C_E but not any of those buried in other handled components. */ if (TREE_CODE (expr) == VIEW_CONVERT_EXPR) expr = TREE_OPERAND (expr, 0); but I couldn't easily convince it to do sth here (and dumps turn out empty as for reasoning of disqualification).
next prev parent reply other threads:[~2023-12-15 13:33 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-04-05 20:29 [Bug tree-optimization/99919] New: [9/10/11 " msebor at gcc dot gnu.org 2021-04-05 20:51 ` [Bug tree-optimization/99919] " msebor at gcc dot gnu.org 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/99919] [9/10/11/12 " rguenth at gcc dot gnu.org 2021-11-30 11:58 ` aldyh at gcc dot gnu.org 2021-11-30 12:06 ` pinskia at gcc dot gnu.org 2021-11-30 14:22 ` aldyh at gcc dot gnu.org 2022-12-08 9:25 ` [Bug tree-optimization/99919] [10/11/12/13 " rguenth at gcc dot gnu.org 2022-12-08 10:47 ` rguenth at gcc dot gnu.org 2023-04-26 6:55 ` [Bug tree-optimization/99919] [10/11/12/13/14 " rguenth at gcc dot gnu.org 2023-07-27 9:22 ` [Bug tree-optimization/99919] [11/12/13/14 " rguenth at gcc dot gnu.org 2023-12-15 13:33 ` rguenth at gcc dot gnu.org [this message] 2024-05-21 9:10 ` [Bug tree-optimization/99919] [11/12/13/14/15 " jakub 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-99919-4-4Vz2kolDh3@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).