From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-bugzilla@gcc.gnu.org>
Received: by sourceware.org (Postfix, from userid 48)
	id 9423B3858C20; Fri,  3 Feb 2023 08:00:25 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 9423B3858C20
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1675411225;
	bh=AIDLUWGGdPUj9a9iJ9l43uBzO80Xn3LywarbRkvcJ/8=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=o+Q6zkMJu0Lr8so61WjIGRI9qGfoysKLws7JWgPGYMFYzYacotVVxSYeORLPQsMVO
	 pcm1SZqO3wB0BDmLgnaZJVpl9mQnSVYMsPjWNZAzBwj6+wWzxwd7X9urWGow2iQ1sC
	 i2MxaPBd923mCt+vWKTkc9m+KRMCxwyR8wamrlng=
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/108644] Format string warnings related to longs under
 MigW-W64/MSYS2 on Windows 10
Date: Fri, 03 Feb 2023 08:00:25 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: other
X-Bugzilla-Version: 13.0
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-108644-4-IySFFTHtRr@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-108644-4@http.gcc.gnu.org/bugzilla/>
References: <bug-108644-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
List-Id: <gcc-bugs.sourceware.org>

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

--- Comment #3 from Richard Biener <rguenth at gcc dot gnu.org> ---
(In reply to Andrew Pinski from comment #1)
> The lto-plugin warnings are not a GCC issue really.
> ../../../gcc/lto-plugin/lto-plugin.c:501:19: warning: 'I' flag used with
> '%x' gnu_printf format [-Wformat=3D]
>=20
>=20
> Those are done correctly and using the right arguments and all. The issue=
 is
> rather how PRI_LL is defined but fprintf specifies gnu_printf rather than
> win32_printf format ....
> Where is PRI_LL definition coming from? Please provide the preprocessed
> source (and add -g3 to keep the #define's in there).
> I suspect there is a bug in mingw's stdint.h in some cases ...

/* We need to use I64 instead of ll width-specifier on native Windows.
   The reason for this is that older MS-runtimes don't support the ll.  */
#ifdef __MINGW32__
#define PRI_LL "I64"
#else
#define PRI_LL "ll"
#endif=