[Bug c/83656] missing -Wbuiltin-declaration-mismatch on declaration without prototype

["ro at gcc dot gnu.org" <gcc-bugzilla at gcc dot gnu dot org>]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83656

Rainer Orth <ro at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |REOPENED
                 CC|                            |ro at gcc dot gnu.org
         Resolution|FIXED                       |---

--- Comment #9 from Rainer Orth <ro at gcc dot gnu.org> ---
I'm seeing the same failure

+FAIL: gcc.dg/Wbuiltin-declaration-mismatch-4.c  (test for warnings, line 80)
+FAIL: gcc.dg/Wbuiltin-declaration-mismatch-4.c  (test for warnings, line 82)
+FAIL: gcc.dg/Wbuiltin-declaration-mismatch-4.c (test for excess errors)

on 32-bit Solaris/SPARC and x86; according to gcc-testresults reports every
32-bit target is affected:

Excess errors:
/vol/gcc/src/hg/trunk/local/gcc/testsuite/gcc.dg/Wbuiltin-declaration-mismatch-4.c:80:17:
warning: 'memset' argument 3 promotes to 'ptrdiff_t' {aka 'int'} where
'unsigned int' is expected in a call to built-in function declared without
prototype [-Wbuiltin-declaration-mismatch]
/vol/gcc/src/hg/trunk/local/gcc/testsuite/gcc.dg/Wbuiltin-declaration-mismatch-4.c:82:17:
warning: 'memset' argument 3 type is 'double' where 'unsigned int' is expected
in a call to built-in function declared without prototype
[-Wbuiltin-declaration-mismatch]

Martin, you'd do us all a great favour if you could test your patches on
32-bit,
too (e.g. a bi-arch Linux/x86_64 build), since there are almost constantly
problems on 32-bit targets.