From: Amir Mazzarella <amirmazz-at-google.com@ffmpeg.org>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] [PATCH] Make implicit void pointer cast explicit
Date: Tue, 19 Jul 2022 14:21:00 -0700
Message-ID: <CAMMoCOf5oawGbi4DPyyFeXOtS_-K3xcAXX7zjG34FSyz8G95+A@mail.gmail.com> (raw)
In-Reply-To: <YtcBLm3QnUgHMINf@phare.normalesup.org>
Thank you for your response! A C++ compiler can't do implicit casts like a
C compiler can, in this instance. This is fine for most of FFmpeg's
codebase, since these tricks are in C source files, but in this instance it
is in a header file. If any C++ code includes this header file, even with
extern "C", it won't be able to be compiled.
On Tue, Jul 19, 2022 at 12:08 PM Nicolas George <george@nsup.org> wrote:
> Hi. Thanks for the patch.
>
> Amir Mazzarella (12022-07-09):
> > Signed-off-by: Amir Mazzarella <amirmazz@google.com>
> > ---
> > libavutil/vulkan_loader.h | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/libavutil/vulkan_loader.h b/libavutil/vulkan_loader.h
> > index 3f1ee6aa46..fa8e5ed171 100644
> > --- a/libavutil/vulkan_loader.h
> > +++ b/libavutil/vulkan_loader.h
> > @@ -82,7 +82,7 @@ static inline int
> ff_vk_load_functions(AVHWDeviceContext *ctx,
> > uint64_t extensions_mask,
> > int has_inst, int has_dev)
> > {
> > - AVVulkanDeviceContext *hwctx = ctx->hwctx;
> > + AVVulkanDeviceContext *hwctx = (AVVulkanDeviceContext *) ctx->hwctx;
> >
> > static const struct FunctionLoadInfo {
> > int req_inst;
>
> Why? What is it supposed to fix?
>
> Regards,
>
> --
> Nicolas George
>
_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link above, or email
ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".
next prev parent reply other threads:[~2022-07-19 21:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-09 4:31 Amir Mazzarella
2022-07-19 18:32 ` Amir Mazzarella
2022-07-19 19:08 ` Nicolas George
2022-07-19 21:21 ` Amir Mazzarella [this message]
2022-07-19 21:23 ` Hendrik Leppkes
2022-07-19 21:23 ` Nicolas George
2022-07-19 22:12 ` Amir Mazzarella
2022-07-20 9:01 ` Nicolas George
2022-07-28 14:11 ` Anton Khirnov
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=CAMMoCOf5oawGbi4DPyyFeXOtS_-K3xcAXX7zjG34FSyz8G95+A@mail.gmail.com \
--to=amirmazz-at-google.com@ffmpeg.org \
--cc=ffmpeg-devel@ffmpeg.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
Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
This inbox may be cloned and mirrored by anyone:
git clone --mirror https://master.gitmailbox.com/ffmpegdev/0 ffmpegdev/git/0.git
# If you have public-inbox 1.1+ installed, you may
# initialize and index your mirror using the following commands:
public-inbox-init -V2 ffmpegdev ffmpegdev/ https://master.gitmailbox.com/ffmpegdev \
ffmpegdev@gitmailbox.com
public-inbox-index ffmpegdev
Example config snippet for mirrors.
AGPL code for this site: git clone https://public-inbox.org/public-inbox.git