public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/39612] [4.3/4.4/4.5 Regression] LIM inserts loads from uninitialized local memory Date: Sun, 26 Apr 2009 17:34:00 -0000 [thread overview] Message-ID: <20090426173438.22021.qmail@sourceware.org> (raw) In-Reply-To: <bug-39612-17519@http.gcc.gnu.org/bugzilla/> ------- Comment #4 from rguenth at gcc dot gnu dot org 2009-04-26 17:34 ------- void foo(int *); void f2(int dst[3], int R) { int i, inter[2]; for (i = 1; i < R; i++) { inter[0] = 1; inter[1] = 1; } foo(inter); } Warns at -Os or also at -O2 if you disable loop header copying. So maybe we should avoid doing loads from local memory in places we do not know will be executed. On trunk simply the warning doesn't work anymore, the loads are still there, same for 4.3. The loads are not removed by any pass (without loop header copying) and the loop remains. Note that even with -Os -ftree-ch no loop header copying is performed. -- rguenth at gcc dot gnu dot org changed: What |Removed |Added ---------------------------------------------------------------------------- Known to work| |4.2.4 Summary|[4.4/4.5 Regression] |[4.3/4.4/4.5 Regression] LIM |Incorrect warning issued Re |inserts loads from |variable *is* used |uninitialized local memory |uninitialized in this | |function | http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39612
next prev parent reply other threads:[~2009-04-26 17:34 UTC|newest] Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top 2009-04-02 4:32 [Bug c/39612] New: Incorrect warning issued Re variable *is* used uninitialized in this function tony at bakeyournoodle dot com 2009-04-02 4:35 ` [Bug c/39612] " tony at bakeyournoodle dot com 2009-04-02 9:44 ` [Bug tree-optimization/39612] [4.4/4.5 Regression] " rguenth at gcc dot gnu dot org 2009-04-03 17:41 ` rakdver at gcc dot gnu dot org 2009-04-14 9:50 ` jakub at gcc dot gnu dot org 2009-04-21 15:58 ` jakub at gcc dot gnu dot org 2009-04-25 22:44 ` rakdver at gcc dot gnu dot org 2009-04-26 17:34 ` rguenth at gcc dot gnu dot org [this message] 2009-04-26 18:37 ` [Bug tree-optimization/39612] [4.3/4.4/4.5 Regression] LIM inserts loads from uninitialized local memory rakdver at gcc dot gnu dot org 2009-04-26 18:45 ` rguenther at suse dot de 2009-04-27 7:24 ` jakub at gcc dot gnu dot org 2009-04-27 8:16 ` rguenther at suse dot de 2009-07-22 10:35 ` jakub at gcc dot gnu dot org 2009-10-05 20:10 ` pinskia at gcc dot gnu dot org 2009-10-15 12:56 ` jakub at gcc dot gnu dot org 2010-01-21 13:19 ` jakub at gcc dot gnu dot org 2010-03-03 20:21 ` pinskia at gcc dot gnu dot org 2010-04-30 8:56 ` [Bug tree-optimization/39612] [4.3/4.4/4.5/4.6 " jakub 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=20090426173438.22021.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).