From: Amir Mazzarella <amirmazz-at-google.com@ffmpeg.org>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] [PATCH] Remove unsafe bitwise OR on FFVulkanExtensions enum
Date: Tue, 19 Jul 2022 11:31:56 -0700
Message-ID: <CAMMoCOcfCC7dGhqCK1S-ghoxPae0kUCyh+PkMr39QOcdVQ_HhQ@mail.gmail.com> (raw)
In-Reply-To: <20220709035723.2035064-1-amirmazz@google.com>
Ping
On Fri, Jul 8, 2022 at 8:57 PM Amir Mazzarella <amirmazz@google.com> wrote:
> FFVulkanExtensions enum does not have a value for 0 defined, and bitwise
> OR on enums is not safe. The function returns uint64_t, so it makes more
> sense and is safer to do arithmetic in terms of uint64_t
>
> Signed-off-by: Amir Mazzarella <amirmazz@google.com>
> ---
> libavutil/vulkan_loader.h | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/libavutil/vulkan_loader.h b/libavutil/vulkan_loader.h
> index 3f1ee6aa46..0b2de4ab94 100644
> --- a/libavutil/vulkan_loader.h
> +++ b/libavutil/vulkan_loader.h
> @@ -50,12 +50,12 @@ static inline uint64_t ff_vk_extensions_to_mask(const
> char * const *extensions,
> #endif
> };
>
> - FFVulkanExtensions mask = 0x0;
> + uint64_t mask = 0x0;
>
> for (int i = 0; i < nb_extensions; i++) {
> for (int j = 0; j < FF_ARRAY_ELEMS(extension_map); j++) {
> if (!strcmp(extensions[i], extension_map[j].name)) {
> - mask |= extension_map[j].flag;
> + mask |= (uint64_t) extension_map[j].flag;
> continue;
> }
> }
> --
> 2.37.0.rc0.161.g10f37bed90-goog
>
>
_______________________________________________
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 18:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-09 3:57 Amir Mazzarella
2022-07-19 18:31 ` Amir Mazzarella [this message]
2022-07-20 4:34 ` Marvin Scholz
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=CAMMoCOcfCC7dGhqCK1S-ghoxPae0kUCyh+PkMr39QOcdVQ_HhQ@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