git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH 5/6] parse-options: add precision handling for OPTION_BITOP

From
Patrick Steinhardt <ps@pks.im>
Date
Jul 2, 2025, 02:33 UTC
Message-ID
<aGSadcpxNsp1BLCm@pks.im>
In-Reply-To
<978e38e1-45b4-4c74-856d-255a87d6c817@web.de>
On Tue, Jul 01, 2025 at 05:21:11PM +0200, René Scharfe wrote:
Show 40 quoted lines
> On 7/1/25 12:55 PM, Patrick Steinhardt wrote:
> > On Sun, Jun 29, 2025 at 01:51:19PM +0200, René Scharfe wrote:
> >> Similar to 09705696f7 (parse-options: introduce precision handling for
> >> `OPTION_INTEGER`, 2025-04-17) support value variables of different sizes
> >> for OPTION_BITOP.  Do that by requiring their "precision" to be set,
> >> casting their "value" pointer accordingly and checking whether the value
> >> fits.
> >>
> >> Checking "defval" has the side-effect of also requiring PARSE_OPT_NOARG.
> > 
> > Hm, requiring PARSE_OPT_NOARG for what? I cannot see it being touched in
> > this patch at all, so I'm a but puzzled.
> 
> For options with OPTION_BITOP.  Adding the defval check also adds the
> no-argument check by falling through to it:
> 
> diff --git a/parse-options.c b/parse-options.c
> index 6bd7158806..0dc9b0324a 100644
> --- a/parse-options.c
> +++ b/parse-options.c
> @@ -620,18 +623,19 @@ static void parse_options_check(const struct option *opts)
>  			optbug(opts, "uses feature "
>  			       "not supported for dashless options");
>  		if (opts->type == OPTION_SET_INT && !opts->defval &&
>  		    opts->long_name && !(opts->flags & PARSE_OPT_NONEG))
>  			optbug(opts, "OPTION_SET_INT 0 should not be negatable");
>  		switch (opts->type) {
>  		case OPTION_SET_INT:
>  		case OPTION_BIT:
>  		case OPTION_NEGBIT:
> +		case OPTION_BITOP:
>  			if (!signed_int_fits(opts->defval, opts->precision))
>  				optbug(opts, "has invalid defval");
>  			/* fallthru */
>  		case OPTION_COUNTUP:
>  		case OPTION_NUMBER:
>  			if ((opts->flags & PARSE_OPT_OPTARG) ||
>  			    !(opts->flags & PARSE_OPT_NOARG))
>  				optbug(opts, "should not accept an argument");
>  			break;

Ah, now I see it, the extended context definitely helps. Might be nice to point out explicitly in the commit message that it's about the fallthrough behaviour.

Patrick
Previous: René ScharfeNext: René Scharfe
Message 14 of 31 in “parse-options: add more precision handling”
  1. 0/6 parse-options: add more precision handlingRené Scharfe, Jun 29, 2025
  2. 1/6 parse-options: add precision handling for PARSE_OPT_CMDMODERené Scharfe, Jun 29, 2025
  3. Patrick SteinhardtJul 1, 2025
  4. René ScharfeJul 1, 2025
  5. 2/6 parse-options: add precision handling for OPTION_SET_INTRené Scharfe, Jun 29, 2025
  6. Patrick SteinhardtJul 1, 2025
  7. René ScharfeJul 1, 2025
  8. Patrick SteinhardtJul 2, 2025
  9. 3/6 parse-options: add precision handling for OPTION_BITRené Scharfe, Jun 29, 2025
  10. 4/6 parse-options: add precision handling for OPTION_NEGBITRené Scharfe, Jun 29, 2025
  11. 5/6 parse-options: add precision handling for OPTION_BITOPRené Scharfe, Jun 29, 2025
  12. Patrick SteinhardtJul 1, 2025
  13. René ScharfeJul 1, 2025
  14. Patrick SteinhardtJul 2, 2025
  15. 6/6 parse-options: add precision handling for OPTION_COUNTUPRené Scharfe, Jun 29, 2025
  16. Patrick SteinhardtJul 1, 2025
  17. René ScharfeJul 1, 2025
  18. Patrick SteinhardtJul 2, 2025
  19. 0/7 parse-options: add more precision handlingRené Scharfe, Jul 9, 2025
  20. 1/7 parse-options: require PARSE_OPT_NOARG for OPTION_BITOPRené Scharfe, Jul 9, 2025
  21. Patrick SteinhardtJul 9, 2025
  22. 2/7 parse-options: add precision handling for PARSE_OPT_CMDMODERené Scharfe, Jul 9, 2025
  23. Patrick SteinhardtJul 9, 2025
  24. René ScharfeJul 9, 2025
  25. Patrick SteinhardtJul 9, 2025
  26. Junio C HamanoJul 9, 2025
  27. 3/7 parse-options: add precision handling for OPTION_SET_INTRené Scharfe, Jul 9, 2025
  28. 4/7 parse-options: add precision handling for OPTION_BITRené Scharfe, Jul 9, 2025
  29. 5/7 parse-options: add precision handling for OPTION_NEGBITRené Scharfe, Jul 9, 2025
  30. 6/7 parse-options: add precision handling for OPTION_BITOPRené Scharfe, Jul 9, 2025
  31. 7/7 parse-options: add precision handling for OPTION_COUNTUPRené Scharfe, Jul 9, 2025

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.