qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Richard Henderson <richard.henderson@linaro.org>
To: "Philippe Mathieu-Daudé" <philmd@linaro.org>, qemu-devel@nongnu.org
Cc: "Alex Bennée" <alex.bennee@linaro.org>
Subject: Re: [PATCH] semihosting/arm-compat: Have TARGET_SYS_EXIT[_EXTENDED] return signed
Date: Tue, 10 Oct 2023 09:16:10 -0700	[thread overview]
Message-ID: <692e508d-ea6f-48fa-a885-dcc32fa2f653@linaro.org> (raw)
In-Reply-To: <20231005062610.57351-1-philmd@linaro.org>

On 10/4/23 23:26, Philippe Mathieu-Daudé wrote:
> Per the "Semihosting for AArch32 and AArch64" spec. v2 (2023Q3) [*]:
> 
>    6.5   SYS_EXIT (0x18)
>    6.5.2   Entry (64-bit)
> 
>      On entry, the PARAMETER REGISTER contains a pointer to
>      a two-field argument block:
> 
>      . field 1
>        The exception type, which is one of the set of reason
>        codes in the above tables.
> 
>      . field 2
>        A subcode, whose meaning depends on the reason code in
>        field 1.
> 
>      In particular, if field 1 is ADP_Stopped_ApplicationExit
>      then field 2 is an exit status code, as passed to the C
>      standard library exit() function. [...]
> 
> Having libc exit() is declared as:
> 
>    LIBRARY
>         Standard C Library (libc, -lc)
> 
>    SYNOPSIS
> 
>         void
>         exit(int status);
> 
> the status is expected to be signed.

Reviewed-by: Richard Henderson <richard.henderson@linaro.org>


r~


  parent reply	other threads:[~2023-10-10 16:17 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-05  6:26 [PATCH] semihosting/arm-compat: Have TARGET_SYS_EXIT[_EXTENDED] return signed Philippe Mathieu-Daudé
2023-10-05 13:32 ` Alex Bennée
2023-10-10 16:16 ` Richard Henderson [this message]
2023-10-16 16:08 ` Peter Maydell
2023-10-17 11:32   ` Philippe Mathieu-Daudé
2023-10-17 12:03     ` Peter Maydell

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=692e508d-ea6f-48fa-a885-dcc32fa2f653@linaro.org \
    --to=richard.henderson@linaro.org \
    --cc=alex.bennee@linaro.org \
    --cc=philmd@linaro.org \
    --cc=qemu-devel@nongnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).