Bug#887320: A Workaround

[Chris Edgington]

Running the as31 under valgrind is also a workaround. This is a clue that the 
problem is likely due to a 32-bit vs 64-bit pointer assumption.

On Sat, 17 Feb 2018 15:38:23 -0800 (PST) "Jason Self"  
wrote:
> gcc -O2 crashes but -O0 and -O1 don't. The assembler probably has old,
> fragile code that relies on assumptions that no longer hold (or that
> never held.)

Bug#887320: A Workaround

[Jason Self]

gcc -O2 crashes but -O0 and -O1 don't. The assembler probably has old,
fragile code that relies on assumptions that no longer hold (or that
never held.)