On Tue, 25 Sep 2018, Andreas Schwab wrote:
On Sep 25 2018, Michael Schmitz <schmitzmic@xxxxxxxxx> wrote:
Hi Finn,
On 25/09/18 11:49, Finn Thain wrote:
On Tue, 25 Sep 2018, Michael Schmitz wrote:
Hi Finn,
has this been resolved in the meantime?
My compiler is too old (4.4.6) to be affected. Also, I didn't pursue a
patch because I don't really know how you fix this properly.
Maybe Andreas or Geert have thought of something?
The right fix is to use strcmp directly.
But it's not always going to be strcmp that has this problem. Also, there
is a lot of developers that you'll need to educate. I'm not sure that
approach is feasible. At least, not without a new compiler warning to
indicate that the compiler is going to attempt a risky optimization.
--
Andreas.
