From: Rosen Penev <rosenp@gmail.com>
To: Hans Verkuil <hverkuil@xs4all.nl>
Cc: linux-media@vger.kernel.org
Subject: Re: [PATCH 5/8] v4l2-info: remove a strange sizeof usage
Date: Wed, 21 Apr 2021 02:39:16 -0700 [thread overview]
Message-ID: <36545438-CED2-4A0A-BF50-90102500E66D@gmail.com> (raw)
In-Reply-To: <9e4086d7-7ea6-7120-4f2d-1609dcdba93e@xs4all.nl>
> On Apr 21, 2021, at 02:33, Hans Verkuil <hverkuil@xs4all.nl> wrote:
>
>> On 21/04/2021 11:19, Rosen Penev wrote:
>>
>>>> On Apr 21, 2021, at 01:23, Hans Verkuil <hverkuil@xs4all.nl> wrote:
>>>>
>>>> On 21/04/2021 09:20, Rosen Penev wrote:
>>>> The array has a nullptr and 0 member for some reason. Remove and convert
>>>> loop to a for range one.
>>>>
>>>> Signed-off-by: Rosen Penev <rosenp@gmail.com>
>>>> ---
>>>> utils/common/v4l2-info.cpp | 33 +++++++++++++++------------------
>>>> 1 file changed, 15 insertions(+), 18 deletions(-)
>>>>
>>>> diff --git a/utils/common/v4l2-info.cpp b/utils/common/v4l2-info.cpp
>>>> index cb3cb91f7..0359cf137 100644
>>>> --- a/utils/common/v4l2-info.cpp
>>>> +++ b/utils/common/v4l2-info.cpp
>>>> @@ -3,6 +3,8 @@
>>>> * Copyright 2018 Cisco Systems, Inc. and/or its affiliates. All rights reserved.
>>>> */
>>>>
>>>> +#include <array>
>>>> +
>>>> #include <v4l2-info.h>
>>>>
>>>> static std::string num2s(unsigned num, bool is_hex = true)
>>>> @@ -411,21 +413,20 @@ std::string mbus2s(unsigned flags, bool is_hsv)
>>>> return flags2s(flags, mbus_ycbcr_def);
>>>> }
>>>>
>>>> -static const flag_def selection_targets_def[] = {
>>>> - { V4L2_SEL_TGT_CROP_ACTIVE, "crop" },
>>>> - { V4L2_SEL_TGT_CROP_DEFAULT, "crop_default" },
>>>> - { V4L2_SEL_TGT_CROP_BOUNDS, "crop_bounds" },
>>>> - { V4L2_SEL_TGT_COMPOSE_ACTIVE, "compose" },
>>>> - { V4L2_SEL_TGT_COMPOSE_DEFAULT, "compose_default" },
>>>> - { V4L2_SEL_TGT_COMPOSE_BOUNDS, "compose_bounds" },
>>>> - { V4L2_SEL_TGT_COMPOSE_PADDED, "compose_padded" },
>>>> - { V4L2_SEL_TGT_NATIVE_SIZE, "native_size" },
>>>> - { 0, nullptr }
>>>
>>> The idea of having this sentinel is that this makes it easy to add new
>>> entries without having to update the array size.
>> Not following this. I assume it’s some C feature.
>
> Standard programming techique:
>
> https://en.wikipedia.org/wiki/Sentinel_value#:~:text=In%20computer%20programming%2C%20a%20sentinel,a%20loop%20or%20recursive%20algorithm.
>
>>>
>>>> +static constexpr std::array<flag_def, 8> selection_targets_def{
>>>
>>> Something you need to do here, adding a new flag means updating the size.
>> I assume this is a small issue. It’s an immediate compile error anyway.
>
> Not if the size is larger that the number of initializers. That would leave
> zeroed elements at the end.
Ah yes that is a real problem. I’ve been bitten by it in the past.
>
>>>
>>> New flags are added regularly, so keeping that robust is a good idea IMHO.
>>>
>>> If it were possible to write:
>>>
>>> static constexpr std::array<flag_def> selection_targets_def{
>>>
>>> i.e. without an explicit size, then this would make sense, but C++
>>> doesn't allow this. And std::vector allocates the data on the heap,
>>> which is less efficient as well.
>> But this is possible. With C++17 :). That would necessitate a minimum of GCC6 though.
>
> How is that done in C++17? I didn't find anything about that.
C++17 has class template argument deduction. It allows putting just std::array or std::vector or any other container really without the <>. Of course you have to allow it to deduce the arguments by putting them in the initializers. This is actually what I did in the previous cec-tuner patch.
>
> Regards,
>
> Hans
>
>>>
>>> Let's just keep using normal arrays in this case, they do the job
>>> just fine. Just because you have a hammer, it doesn't mean everything
>>> is now a nail :-)
>>>
>>> Regards,
>>>
>>> Hans
>>>
>>>> + flag_def{ V4L2_SEL_TGT_CROP_ACTIVE, "crop" },
>>>> + flag_def{ V4L2_SEL_TGT_CROP_DEFAULT, "crop_default" },
>>>> + flag_def{ V4L2_SEL_TGT_CROP_BOUNDS, "crop_bounds" },
>>>> + flag_def{ V4L2_SEL_TGT_COMPOSE_ACTIVE, "compose" },
>>>> + flag_def{ V4L2_SEL_TGT_COMPOSE_DEFAULT, "compose_default" },
>>>> + flag_def{ V4L2_SEL_TGT_COMPOSE_BOUNDS, "compose_bounds" },
>>>> + flag_def{ V4L2_SEL_TGT_COMPOSE_PADDED, "compose_padded" },
>>>> + flag_def{ V4L2_SEL_TGT_NATIVE_SIZE, "native_size" },
>>>> };
>>>>
>>>> bool valid_seltarget_at_idx(unsigned i)
>>>> {
>>>> - return i < sizeof(selection_targets_def) / sizeof(selection_targets_def[0]) - 1;
>>>> + return i < selection_targets_def.size();
>>>> }
>>>>
>>>> unsigned seltarget_at_idx(unsigned i)
>>>> @@ -437,13 +438,9 @@ unsigned seltarget_at_idx(unsigned i)
>>>>
>>>> std::string seltarget2s(__u32 target)
>>>> {
>>>> - int i = 0;
>>>> -
>>>> - while (selection_targets_def[i].str != nullptr) {
>>>> - if (selection_targets_def[i].flag == target)
>>>> - return selection_targets_def[i].str;
>>>> - i++;
>>>> - }
>>>> + for (const auto &def : selection_targets_def)
>>>> + if (def.flag == target)
>>>> + return def.str;
>>>> return std::string("Unknown (") + num2s(target) + ")";
>>>> }
>>>>
>>>>
>>>
>
next prev parent reply other threads:[~2021-04-21 9:39 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-21 7:20 [PATCH 1/8] clang-tidy: use auto Rosen Penev
2021-04-21 7:20 ` [PATCH 2/8] clang-tidy: use nullptr Rosen Penev
2021-04-21 7:20 ` [PATCH 3/8] remove unused ARRAY_SIZE Rosen Penev
2021-04-21 7:20 ` [PATCH 4/8] cec-tuner: std::array conversions Rosen Penev
2021-04-21 7:20 ` [PATCH 5/8] v4l2-info: remove a strange sizeof usage Rosen Penev
2021-04-21 8:23 ` Hans Verkuil
2021-04-21 9:19 ` Rosen Penev
2021-04-21 9:33 ` Hans Verkuil
2021-04-21 9:39 ` Rosen Penev [this message]
2021-04-21 16:01 ` Nicolas Dufresne
2021-04-21 7:20 ` [PATCH 6/8] v4l2-utils: turn fb_formats to constexpr array Rosen Penev
2021-04-21 7:20 ` [PATCH 7/8] v4l2-utils: turn mbus_names into const vector Rosen Penev
2021-04-21 8:02 ` Hans Verkuil
2021-04-21 9:25 ` Rosen Penev
2021-04-21 7:20 ` [PATCH 8/8] v4l2-utils: turn prefixes to a constexpr array Rosen Penev
2021-04-21 8:06 ` Hans Verkuil
2021-04-21 9:23 ` Rosen Penev
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=36545438-CED2-4A0A-BF50-90102500E66D@gmail.com \
--to=rosenp@gmail.com \
--cc=hverkuil@xs4all.nl \
--cc=linux-media@vger.kernel.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).