public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "gabravier at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/98908] Failure to optimize arithmetic involving struct members into operating on the entire struct
Date: Fri, 03 Sep 2021 01:09:13 +0000	[thread overview]
Message-ID: <bug-98908-4-vYw3Yyrwoj@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-98908-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #8 from Gabriel Ravier <gabravier at gmail dot com> ---
Well, fixing a bug filed in 2021 in GCC 9 seems quite hard. Are you confused
about the nature of the bug ? The first example in the description *is* the one
whose optimization the bug is about, and it is the one that didn't optimize
properly in trunk at the time of the bug being filed, back when trunk was GCC
11.0. I'm pretty sure this bug should be considering as fixed for GCC 12
considering it seems to have been fixed somewhere between GCC 11 (which has the
bad code generation) and trunk (which doesn't).

  parent reply	other threads:[~2021-09-03  1:09 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-01  8:10 [Bug tree-optimization/98908] New: " gabravier at gmail dot com
2021-02-02  7:58 ` [Bug tree-optimization/98908] " rguenth at gcc dot gnu.org
2021-09-03  0:15 ` gabravier at gmail dot com
2021-09-03  0:27 ` pinskia at gcc dot gnu.org
2021-09-03  0:28 ` pinskia at gcc dot gnu.org
2021-09-03  0:31 ` gabravier at gmail dot com
2021-09-03  0:41 ` gabravier at gmail dot com
2021-09-03  0:59 ` pinskia at gcc dot gnu.org
2021-09-03  1:09 ` gabravier at gmail dot com [this message]
2021-09-03  1:11 ` gabravier at gmail dot com
2021-09-03  1:31 ` [Bug tree-optimization/98908] [11 Regression] arithmetic involving struct members into operating on the entire struct fails at -O3 pinskia at gcc dot gnu.org
2021-09-03  1:38 ` pinskia at gcc dot gnu.org
2022-04-21  7:48 ` rguenth at gcc dot gnu.org
2023-05-29 10:04 ` 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-98908-4-vYw3Yyrwoj@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).