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/44736] Overeager -O1 optimization results in incorrect code generation Date: Thu, 01 Jul 2010 08:21:00 -0000 [thread overview] Message-ID: <20100701082050.7784.qmail@sourceware.org> (raw) In-Reply-To: <bug-44736-19385@http.gcc.gnu.org/bugzilla/> ------- Comment #3 from rguenth at gcc dot gnu dot org 2010-07-01 08:20 ------- (In reply to comment #2) > Thanks for the lightening fast response. I wouldn't have known to look there, > especially since older GCC versions did not have this problem. > > Is it because 4.5.0 has better optimizations such that the code surrounding > this malloc is now optimized away in this situation? > > Finally, is this issue going to be resolved within GCC, or is the permanent fix > going to be to ask developers to use -fno-builtin-malloc? We are going to ask developers to use -fno-builtin-malloc for now. I also think this is a glibc bug which should mark the hook variables volatile. So, can you file a bug in the glibc bugzilla as well? > Thanks again. > -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44736
next prev parent reply other threads:[~2010-07-01 8:21 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2010-06-30 23:36 [Bug c/44736] New: " opensource3141 at gmail dot com 2010-06-30 23:42 ` [Bug tree-optimization/44736] " pinskia at gcc dot gnu dot org 2010-07-01 0:33 ` opensource3141 at gmail dot com 2010-07-01 8:21 ` rguenth at gcc dot gnu dot org [this message] 2010-07-01 16:52 ` opensource3141 at gmail dot com
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=20100701082050.7784.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).