News for hackers. Stuff that matters.
Re:Can We Trust the Libraries We Use? by nullc on Monday August 11, 2014 @07:29AM (#8162830)
> A variable is assigned its own value.

Self assignment is used to silence overly aggressive and incorrect uninitialized warnings in GCC (esp prior to 4.5).

I'm not sure if thats what the code there is doing— not enough context, but I'd guess it's likely. Odd that the author hasn't seen that before.

Re:Can We Trust the Libraries We Use? by tokenrove on Monday August 11, 2014 @08:01AM (#8162891)
That seems unlikely to be the case; the variable being assigned is through a pointer to a struct, which is already being accessed in the context. (Plus, of course, __attribute__((unused)) or similar in a macro would be preferable for silencing warnings) It's pretty likely that, had this occured at the top of a function, and been a direct assignment, the author would not have flagged it (indeed, perhaps PVS-Studio ignores that case; seems easy enough to implement).
Re:Can We Trust the Libraries We Use? by Mathiasdm on Monday August 11, 2014 @11:44AM (#8163722)
__attribute__((unused)) indeed would be the best option when using gcc. I believe when using C++11, this can be replaced by [[gnu::unused]].

Another one that I've seen quite often is casting to void.

Re:Can We Trust the Libraries We Use? by nullc on Friday August 15, 2014 @09:09PM (#8185061)
Not unused. Uninitialized.

E.g. in older GCC you would get int x; switch (!!foo) { case 0:x=0;break; case 1:x=1;break; /no default/ } print(..x)

Or many other cases and the compiler will give an erroneous uninitialized warning. you can assign x to itself at the stop to eliminate the warning without changing the generated code.