libc: Implement N2630.

[des]

Summary

This adds formatted input/output of binary integer numbers to the printf(), scanf(), and strtol() families, including their wide-character counterparts.

[des]

add missing L prefixes

[imp]

With all the code repetitions, you'd think a macro might not be bad to have for all the places that need to do this parsing.
It's no worse than what we have today, but as the number of cases have grown, it's starting to be difficult to manage.

lib/libc/iconv/_strtol.h

96

'0' || == '1'

also would work, but I'm not sure it would generate better code and so might not be worth breaking the pattern with the other bases.
And should it be an 'else if'?

[imp]

Also, it might make sense to include a pointer to what N2630 is or a spec or something. Google doesn't give me good search results when I look for it without getting kinda specific. A simple URL for the commit message would do wonders.

[emaste]

Also, it might make sense to include a pointer to what N2630 is or a spec or something

Yeah, and reference it in the commit message subject too. N2630 doesn't mean much to me but something like "base 2 support for printf/scanf et al" would be useful

I'm not convinced using macros for these functions is going to be straightforward / make things more clear.

lib/libc/stdio/vfscanf.c

441

should p == start on the next line for style(9)?

[des]

Reimplement parseint() as a finite state machine.

[imp]

fsm ftw lgtm

[des]

Fix vfwscanf().

[des]

Fix count in "0b" / "0x" case.

[des]

Fix remaining bugs revealed by improved tests.

[des]

Fix non-EOF case.

[imp]

Still thing that having a 'is_prefix_binary()' macro would make the code cleaner and avoid a lot of duplication (that admittedly we put up with for hex, there should be one for that too), but I lost that argument in the reviews...

[des]

In D41511#948412, @imp wrote:

Still thing that having a 'is_prefix_binary()' macro would make the code cleaner and avoid a lot of duplication (that admittedly we put up with for hex, there should be one for that too), but I lost that argument in the reviews...

Most of the added complexity arises from the fact that the binary prefix is also a valid hexadecimal number... in fact, any binary number, with or without prefix, is also a valid unprefixed hexadecimal number. And we need to handle all cases with at most one character of look-ahead since that's all we're guaranteed to be able to push back to the stream.