X-Git-Url: http://git.megacz.com/?p=ghc-hetmet.git;a=blobdiff_plain;f=rts%2FRetainerProfile.c;h=17f5afb615d3cdd305334260437db429e2a88b54;hp=cd0001311d294596f5a1d6e148e569b58d9de802;hb=37a3e47992bd46a3cf4f6a4c6fd5b9e187e88452;hpb=ab0e778ccfde61aed4c22679b24d175fc6cc9bf3

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