On Thu, Nov 22, 2018 at 09:58:55AM -0800, Philip Guenther wrote:
> On Thu, 22 Nov 2018, Andreas Kusalananda Kähäri wrote:
> > >Description:
> > When using scanf() to read a value into a uint_fast8_t or uint_fast16_t
> > variable (or the signed equivalent), there is a mismatch between the
> > type of the variable and the format specification that the corresponding
> > SCN{u,d}FAST{8,16} macro expands to.
> >
> > This seems to affect the {u,}int_fast{8,16}_t types and not the "least"
> > variant or ordinary {u,}int{8,16}_t types.
> >
> > This gives rise to warnings from clang, and also affects the values that
> > are stored in the variables (see below).
>
> Your code looks correct to me; <inttypes.h> seems incorrect.
>
> oks for the diff below?
>
[cut]
I saw the patch go into the tree.
Much appreciated, thanks!
--
Andreas Kusalananda Kähäri,
National Bioinformatics Infrastructure Sweden (NBIS),
Uppsala University, Sweden.
