On 30/01/15 11:11, David Malcolm wrote:
> libgccjit can make repeated in-process calls to the compiler code.
>
> On arm I see failures where e.g. the top of the generated .s file has:
> on the 1st iteration:
> .arch armv7-a
> on the 2nd iteration:
> .cpu armv7-a
> without changing any options.
libgccjit can make repeated in-process calls to the compiler code.
On arm I see failures where e.g. the top of the generated .s file has:
on the 1st iteration:
.arch armv7-a
on the 2nd iteration:
.cpu armv7-a
without changing any options.
What's happening is the 1st time through arm_option_ov
