From 37a3e47992bd46a3cf4f6a4c6fd5b9e187e88452 Mon Sep 17 00:00:00 2001 From: "sven.panne@aedion.de" Date: Fri, 10 Nov 2006 16:26:54 +0000 Subject: [PATCH] Added a comment about se.info.type being used uninitialized --- rts/RetainerProfile.c | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/rts/RetainerProfile.c b/rts/RetainerProfile.c index cd00013..17f5afb 100644 --- a/rts/RetainerProfile.c +++ b/rts/RetainerProfile.c @@ -662,6 +662,12 @@ push( StgClosure *c, retainer c_child_r, StgClosure **first_child ) // following statement by either a memcpy() call or a switch statement // on the type of the element. Currently, the size of stackElement is // small enough (5 words) that this direct assignment seems to be enough. + + // ToDo: The line below leads to the warning: + // warning: 'se.info.type' may be used uninitialized in this function + // This is caused by the fact that there are execution paths through the + // large switch statement above where some cases do not initialize this + // field. Is this really harmless? Can we avoid the warning? *stackTop = se; #ifdef DEBUG_RETAINER -- 1.7.10.4