--- Comment #6 from jwbates at mac dot com 2009-05-26 05:26 ---
Update: after some restructuring, the problem still occurs when using the -g
flag, but does not occur when the -O flag is used.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=40036
--- 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
--- Comment #3 from jwbates at mac dot com 2009-05-06 05:25 ---
Not sure at all, as I have very little experience dealing with this kind of
issue. To clarify one point of ambiguity: when I mentioned swapping the order
of the arguments to match the correct evaluation behaviour. So, my
--- Comment #1 from jwbates at mac dot com 2009-05-06 04:09 ---
Created an attachment (id=17806)
--> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=17806&action=view)
output of g++ -save-temps
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=40036
nds.
--
Summary: Initializer incorrectly reordering arguments
Product: gcc
Version: 4.3.2
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: jwba
