public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "k.even-mendoza at imperial dot ac.uk" <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 18:02:26 +0000 [thread overview] Message-ID: <bug-102606-4-njdFNZ54e7@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 --- Comment #4 from Karine EM <k.even-mendoza at imperial dot ac.uk> --- That would make sense, and I think it is also what happens when compiling the example with Clang and -O0 since the compilation takes only a few seconds then.
next prev parent reply other threads:[~2021-10-05 18:02 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 2021-10-05 18:02 ` k.even-mendoza at imperial dot ac.uk [this message] 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-njdFNZ54e7@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).