public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
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	[thread overview]
Message-ID: <bug-108644-4-IySFFTHtRr@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-108644-4@http.gcc.gnu.org/bugzilla/>

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

--- 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=]
> 
> 
> 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

  parent reply	other threads:[~2023-02-03  8:00 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-02 20:10 [Bug other/108644] New: " jdx at o2 dot pl
2023-02-02 20:26 ` [Bug other/108644] " pinskia at gcc dot gnu.org
2023-02-02 20:28 ` pinskia at gcc dot gnu.org
2023-02-03  8:00 ` rguenth at gcc dot gnu.org [this message]
2023-02-03 17:18 ` jdx at o2 dot pl
2023-02-03 17:33 ` jdx at o2 dot pl
2023-02-03 17:37 ` pinskia at gcc dot gnu.org
2023-02-03 17:48 ` jdx at o2 dot pl
2024-02-18  7:55 ` nightstrike at gmail dot com

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-108644-4-IySFFTHtRr@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).