https://sourceware.org/bugzilla/show_bug.cgi?id=22870
Alexandre Oliva changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://sourceware.org/bugzilla/show_bug.cgi?id=22870
Alexandre Oliva changed:
What|Removed |Added
Status|NEW |ASSIGNED
Assignee|unassig
https://sourceware.org/bugzilla/show_bug.cgi?id=22870
Alexandre Oliva changed:
What|Removed |Added
CC||aoliva at sourceware dot org
--- Co
https://sourceware.org/bugzilla/show_bug.cgi?id=22870
--- Comment #3 from Alan Modra ---
> GCC can and should avoid these long chains, issuing view
> reset asserts after insns known to generate code.
That suggest a solution. The assembler certainly knowns when code has been
generated, so can it
https://sourceware.org/bugzilla/show_bug.cgi?id=22870
--- Comment #2 from Alexandre Oliva ---
I suspect the source of the problem is the lack of view reset asserts.
Without that, the assembler gets an uninterrupted chain
of symbolic views, in which each view is computed based on the view
before
https://sourceware.org/bugzilla/show_bug.cgi?id=22870
Alan Modra changed:
What|Removed |Added
CC||amodra at gmail dot com
--- Comment #1 f