Le 06/09/2019 à 18:55, Max Filippov a écrit :
> On Fri, Sep 6, 2019 at 2:33 AM Laurent Vivier wrote:
>> Le 26/08/2019 à 21:58, Max Filippov a écrit :
>>> +#if defined(TARGET_XTENSA)
>>> +if (getenv("QEMU_XTENSA_ABI_CALL0")) {
>>> +xtensa_set_abi_call0();
>>> +}
>>
>> Not needed, th
On Fri, Sep 6, 2019 at 2:33 AM Laurent Vivier wrote:
> Le 26/08/2019 à 21:58, Max Filippov a écrit :
> > +#if defined(TARGET_XTENSA)
> > +if (getenv("QEMU_XTENSA_ABI_CALL0")) {
> > +xtensa_set_abi_call0();
> > +}
>
> Not needed, this is done by parse_args() that checks
> getenv(arg
Le 26/08/2019 à 21:58, Max Filippov a écrit :
> Xtensa binaries built for call0 ABI don't rotate register window on
> function calls and returns. Invocation of signal handlers from the
> kernel is therefore different in windowed and call0 ABIs.
> There's currently no way to determine xtensa ELF bin
Hi Laurent,
On Mon, Aug 26, 2019 at 12:58 PM Max Filippov wrote:
>
> Xtensa binaries built for call0 ABI don't rotate register window on
> function calls and returns. Invocation of signal handlers from the
> kernel is therefore different in windowed and call0 ABIs.
> There's currently no way to d
Xtensa binaries built for call0 ABI don't rotate register window on
function calls and returns. Invocation of signal handlers from the
kernel is therefore different in windowed and call0 ABIs.
There's currently no way to determine xtensa ELF binary ABI from the
binary itself. Add handler for the -x
