From: Peter Maydell <peter.maydell@linaro.org>
To: Akihiko Odaki <akihiko.odaki@gmail.com>
Cc: QEMU Developers <qemu-devel@nongnu.org>,
Gerd Hoffmann <kraxel@redhat.com>
Subject: Re: [PATCH] ui/cocoa: Do not perform unsafe cast of argv
Date: Thu, 8 Jul 2021 10:01:20 +0100 [thread overview]
Message-ID: <CAFEAcA9tjQXMpfJ9MfDWXLOeezh8hfEaDpc0girQ7hEn2XK_Ww@mail.gmail.com> (raw)
In-Reply-To: <20210708054601.9484-1-akihiko.odaki@gmail.com>
On Thu, 8 Jul 2021 at 06:46, Akihiko Odaki <akihiko.odaki@gmail.com> wrote:
>
> Signed-off-by: Akihiko Odaki <akihiko.odaki@gmail.com>
> ---
> ui/cocoa.m | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/ui/cocoa.m b/ui/cocoa.m
> index 9f72844b079..68a6302184a 100644
> --- a/ui/cocoa.m
> +++ b/ui/cocoa.m
> @@ -1888,12 +1888,12 @@ static void cocoa_clipboard_request(QemuClipboardInfo *info,
> exit(status);
> }
>
> -int main (int argc, const char * argv[]) {
> +int main (int argc, char **argv) {
> QemuThread thread;
>
> COCOA_DEBUG("Entered main()\n");
> gArgc = argc;
> - gArgv = (char **)argv;
> + gArgv = argv;
>
> qemu_sem_init(&display_init_sem, 0);
> qemu_sem_init(&app_started_sem, 0);
> --
> 2.30.1 (Apple Git-130)
Why do you consider this cast "unsafe" ? If it's unsafe, then
all we've done is move the unsafety from the cast upwards to the
function prototype. I think what we're really doing here is fixing
the broken prototype of 'main', which should not have 'const'
because that's not how the C standard defines it.
Reviewed-by: Peter Maydell <peter.maydell@linaro.org>
for the code change; you might want to adjust the commit message.
thanks
-- PMM
prev parent reply other threads:[~2021-07-08 9:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-08 5:46 [PATCH] ui/cocoa: Do not perform unsafe cast of argv Akihiko Odaki
2021-07-08 9:01 ` Peter Maydell [this message]
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=CAFEAcA9tjQXMpfJ9MfDWXLOeezh8hfEaDpc0girQ7hEn2XK_Ww@mail.gmail.com \
--to=peter.maydell@linaro.org \
--cc=akihiko.odaki@gmail.com \
--cc=kraxel@redhat.com \
--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).