From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 20306 invoked by alias); 6 May 2009 06:40:03 -0000 Received: (qmail 19491 invoked by uid 48); 6 May 2009 06:39:11 -0000 Date: Wed, 06 May 2009 06:40:00 -0000 Message-ID: <20090506063911.19490.qmail@sourceware.org> X-Bugzilla-Reason: CC References: Subject: [Bug c++/40036] Initializer incorrectly reordering arguments In-Reply-To: Reply-To: gcc-bugzilla@gcc.gnu.org To: gcc-bugs@gcc.gnu.org From: "jwbates at mac 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: 2009-05/txt/msg00402.txt.bz2 ------- Comment #5 from jwbates at mac dot com 2009-05-06 06:39 ------- All of the uninitialized memory errors in valgrind appear to occur after I do the computation, when I'm just trying to print the results. I can convince myself that there's a good chance that the address swap is leaving big chunks of my real data out in the cold, beyond my control. I mean, if all of my data is sitting in my lhs, and that's being used as the rhs, then it won't get touched. And for what it's worth, when I run valgrind on a version compiled with icc, I get no memory errors. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=40036