On 02/24/15 10:29, Chen Gang S wrote:
On 2/25/15 01:03, augustine.sterl...@gmail.com wrote:
On Tue, Feb 24, 2015 at 9:05 AM, Chen Gang S <gang.c...@sunrus.com.cn> wrote:
- After this patch, it can continue compiling, but can we be sure that
it always generates correct code for execution?
After this patch, it should be no worse than it was--lucky.
Someone is working on fixing the underlying xtensa pattern in the
short term. So I would continue whether or not the generated code is
correct.
Another short-term option would be to use an xtensa config that
doesn't have zero-over-head loops.
OK, thank you for your response.
So for me, I shall let genrecog report error instead of warning when it
find this issue, next.
Yes, I think an error would be appropriate here. That way nobody has to
debug same issue you just did in find_reloads.
jeff
