public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "kazu at cs dot umass dot edu" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/17046] An unused array is not optimized away. Date: Mon, 16 Aug 2004 07:31:00 -0000 [thread overview] Message-ID: <20040816073156.32281.qmail@sourceware.org> (raw) In-Reply-To: <20040816065645.17046.kazu@cs.umass.edu> ------- Additional Comments From kazu at cs dot umass dot edu 2004-08-16 07:31 ------- Yes. In fact, the following piece of code does *not* generate the array in the assembly output. static const int banana[] = { 0, 1, 2, 3 }; int foo (void) { return banana[2] * 0; } Note that the fix for this bug is important so that we can cleanly fix PR 14841 because uses of "static const arrays" may disappear during tree optimization. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=17046
next prev parent reply other threads:[~2004-08-16 7:31 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2004-08-16 6:56 [Bug tree-optimization/17046] New: " kazu at cs dot umass dot edu 2004-08-16 7:02 ` [Bug tree-optimization/17046] " pinskia at gcc dot gnu dot org 2004-08-16 7:31 ` kazu at cs dot umass dot edu [this message] 2005-05-04 2:16 ` pinskia at gcc dot gnu dot 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=20040816073156.32281.qmail@sourceware.org \ --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).