27 Aug
2014
27 Aug
'14
12:37 p.m.
Dne st 27. srpna 2014 Michele Calgaro napsal(a):
Slavek,
the problem is not in the C++ code, but clearly in the compiler.
If you google a little you can see we are not the only one affected :) The
problem is probably caused by the addition in: "[0 D.20205_111->m_sbyte+0
S1 A64]))"
even though it is not clear to me why the compiler generate such code since
I didn't see any addition in the C++ code. Since your patch works and it is
quite simple, just push it. The comment in place will remind us of why the
change was necessary.
Cheers
Michele
Exactly so. Also, I've searched for informations. And I found the advice to
change gcc to 4.7 or turn off O2 optimization. Both to me seemed as a more
substantial intervention than a small simple patch from the initial mail.
Pushed to GIT in hash 5a8694bb.
--
Slavek
It's a little "less invasive". If it
doesn't work (hidden compiler
mystery....), just go ahead and push your patch. Cheers
I tried - still the same FTBFS with reference to a compiler bug.
Any other suggestions? :)