News for hackers. Stuff that matters.
Re:GCC 6.1 Released by yrro on Wednesday April 27, 2016 @01:54PM (#11582799)
AIUI, this code is not affected:

  X *foo = ...;
  if (foo) foo->bar();
But this code will be:

  X *foo = ...;
  foo->bar();
  if (foo) { ... }
Since foo is dereferenced unconditionally, the compiler is allowed to assume that it will not be null in the above code, and therefore the test on the third line to determine whether foo is null or not is useless and can be omitted.
Re:GCC 6.1 Released by iso-8859-1 on Wednesday April 27, 2016 @04:28PM (#11584237)
Since this code is broken, wouldn't it be better to emit a warning and let the programmer fix it?
Re:GCC 6.1 Released by caf on Friday April 29, 2016 @09:28AM (#11595547)
The real case where it matters is where the "if (foo) { ... }" test happens in a function that's been inlined into the caller, but not all the callers do the foo->bar() dereference. So it's only being removed in some cases.
Re:GCC 6.1 Released by brandmeyer on Wednesday April 27, 2016 @04:40PM (#11584331)
There used to be a fairly broad warning (-Wunreachable-code), but it caused so many false positives and false negatives that it was removed.