On Wed, Feb 20, 2019 at 10:18:38PM +1100, Michael Ellerman wrote:
> Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx> writes:
> > On Mon, Feb 18, 2019 at 11:49:18AM +1100, Michael Ellerman wrote:
> >> Balbir Singh <bsingharora@xxxxxxxxx> writes:
> >> > Fair enough, my point was that the compiler can help out. I'll see what
> >> > -Wconversion finds on my local build :)
> >>
> >> I get about 43MB of warnings here :)
> >
> > Yes, -Wconversion complains about a lot of things that are idiomatic C.
> > There is a reason -Wconversion is not in -Wall or -Wextra.
>
> Actually a lot of those go away when I add -Wno-sign-conversion.
>
> And what's left seems mostly reasonable, they all indicate the
> possibility of a bug I think.
>
> In fact this works and would have caught the bug:
>
> diff --git a/arch/powerpc/include/asm/book3s/64/pgtable.h b/arch/powerpc/include/asm/book3s/64/pgtable.h
> index d8c8d7c9df15..3114e3f368e2 100644
> --- a/arch/powerpc/include/asm/book3s/64/pgtable.h
> +++ b/arch/powerpc/include/asm/book3s/64/pgtable.h
> @@ -904,7 +904,12 @@ static inline int pud_none(pud_t pud)
>
> static inline int pud_present(pud_t pud)
> {
> + __diag_push();
> + __diag_warn(GCC, 8, "-Wconversion", "ulong -> int");
> +
> return !!(pud_raw(pud) & cpu_to_be64(_PAGE_PRESENT));
> +
> + __diag_pop();
> }
>
> extern struct page *pud_page(pud_t pud);
>
>
>
> Obviously we're not going to instrument every function like that. But we
> could start instrumenting particular files.
So you want to instrument the functions that you know are buggy, using some
weird incantations to catch only those errors you already know about?
(I am worried this does not scale, in many dimensions).
Segher
