The -variable one is http://llvm.org/bugs/show_bug.cgi?id=9824 , I didn’t find a bug for -parameter. The bug has some discussion (and not one but two rdar numbers :-P).
The -variable one is http://llvm.org/bugs/show_bug.cgi?id=9824 , I didn't
find a bug for -parameter. The bug has some discussion (and not one but two
rdar numbers :-P).
From what I understand, the bug still hasn't been fixed; and I would
love for it to be fixed now. From the discussion, it seems that I
just have to hook into the static analyzer's dead-store check? Can you
give me some pointers on where I should be looking? (I'm currently
looking at Sema::DiagnoseUnusedParameters).
The -variable one is http://llvm.org/bugs/show_bug.cgi?id=9824 , I didn’t
find a bug for -parameter. The bug has some discussion (and not one but two
rdar numbers :-P).
From what I understand, the bug still hasn’t been fixed; and I would
love for it to be fixed now. From the discussion, it seems that I
just have to hook into the static analyzer’s dead-store check?
I expect its not /quite/ that simple, but don’t know for sure. I personally would start by looking at the implementation of -Wsometimes-uninitialized & use a similar (but different) cfg/use/def walk.
Can you
give me some pointers on where I should be looking? (I’m currently
looking at Sema::DiagnoseUnusedParameters).
I suppose that’s an interesting if place to look, but I doubt we store the necessary bits for this warning (to differentiate a variable that only written to from one that has reads and writes)