From: Liu Hao <lh_mouse@126.com>
To: "gcc-help@gcc.gnu.org" <gcc-help@gcc.gnu.org>,
"mingw-w64-public@lists.sourceforge.net"
<mingw-w64-public@lists.sourceforge.net>
Subject: mingw-w64 and __attribute__((format(printf))) issue
Date: Wed, 6 May 2020 13:36:13 +0800 [thread overview]
Message-ID: <84f2a94f-0d73-fe05-78c6-bd64c1f8ee76@126.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1159 bytes --]
Due to a recent change in mingw-w64 master [1], libgomp ceases to build:
```
../../../gcc-git/libgomp/target.c:936:21: error: unknown conversion type
character 'l' in format [-Werror=format=]
936 | gomp_fatal ("present clause: !acc_is_present (%p, "
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
```
On line 29 of 'libgomp/libgomp.h' from GCC 9 branch I found this declaration
```
extern void gomp_fatal (const char *, ...)
__attribute__ ((noreturn, format (printf, 1, 2)));
```
, which uses the `printf` attribute, but the `PRIu64` macro from
<inttypes.h> expands to `%llu` because now GCC has `-std=gnu11` by
default, which is only valid with `gnu_printf`.
AFAICS there are three solutions:
1. Revert bfd33f6c0ec5e652cc9911857dd1492ece8d8383 in mingw-w64, or
2. Make GCC treat `format(printf)` as `format(gnu_printf)` if C11 or
C++11 is selected, or
3. Replace `format(printf)` with `format(gnu_printf)` in libgomp source.
What do you think?
[1]
https://github.com/mingw-w64/mingw-w64/commit/bfd33f6c0ec5e652cc9911857dd1492ece8d8383
--
Best regards,
LH_Mouse
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next reply other threads:[~2020-05-06 5:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-06 5:36 Liu Hao [this message]
2020-05-06 10:48 ` [Mingw-w64-public] " Martin Storsjö
2020-05-06 12:45 ` Liu Hao
2020-05-07 4:09 ` Liu Hao
2020-05-10 4:27 ` JonY
2020-05-10 9:03 ` Liu Hao
2020-05-12 11:14 ` JonY
2020-05-12 12:02 ` Jakub Jelinek
2020-05-12 13:15 ` Liu Hao
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=84f2a94f-0d73-fe05-78c6-bd64c1f8ee76@126.com \
--to=lh_mouse@126.com \
--cc=gcc-help@gcc.gnu.org \
--cc=mingw-w64-public@lists.sourceforge.net \
/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).