public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/102606] large array in a dead-code is not optimized away at -O0
Date: Tue, 05 Oct 2021 16:17:46 +0000	[thread overview]
Message-ID: <bug-102606-4-IbvMpNp90n@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-102606-4@http.gcc.gnu.org/bugzilla/>

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

Jakub Jelinek <jakub at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |jakub at gcc dot gnu.org

--- Comment #3 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Or VLA.
Anyway, even at -O0 we can optimize away some if (0)s, but we need assurance
that there are no labels in there and that the code really dead.  So, e.g. if
constexpr (0) can be optimized away because there is a language guarantee that
one can't jump into those bodies.

  parent reply	other threads:[~2021-10-05 16:17 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-05 11:48 [Bug c/102606] New: miscompilation of a program with large array in a dead-code k.even-mendoza at imperial dot ac.uk
2021-10-05 11:52 ` [Bug middle-end/102606] large array in a dead-code is not optimized away at -O0 pinskia at gcc dot gnu.org
2021-10-05 12:08 ` rguenth at gcc dot gnu.org
2021-10-05 16:17 ` jakub at gcc dot gnu.org [this message]
2021-10-05 18:02 ` k.even-mendoza at imperial dot ac.uk
2021-10-08 20:47 ` 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-102606-4-IbvMpNp90n@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).