From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 6120 invoked by alias); 1 Jul 2010 00:33:00 -0000 Received: (qmail 6099 invoked by uid 48); 1 Jul 2010 00:32:51 -0000 Date: Thu, 01 Jul 2010 00:33:00 -0000 Message-ID: <20100701003251.6098.qmail@sourceware.org> X-Bugzilla-Reason: CC References: Subject: [Bug tree-optimization/44736] Overeager -O1 optimization results in incorrect code generation In-Reply-To: Reply-To: gcc-bugzilla@gcc.gnu.org To: gcc-bugs@gcc.gnu.org From: "opensource3141 at gmail dot com" Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org X-SW-Source: 2010-07/txt/msg00001.txt.bz2 ------- Comment #2 from opensource3141 at gmail dot com 2010-07-01 00:32 ------- 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? Thanks again. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44736