From: Jan Kiszka <jan.kiszka@web.de>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: Blue Swirl <blauwirbel@gmail.com>, qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH] mingw: Do not perform string format checks
Date: Mon, 15 Jun 2009 21:50:36 +0200 [thread overview]
Message-ID: <4A36A60C.2000904@web.de> (raw)
In-Reply-To: <alpine.DEB.1.00.0906142209250.26154@pacific.mpi-cbg.de>
[-- Attachment #1: Type: text/plain, Size: 1269 bytes --]
Johannes Schindelin wrote:
> Hi,
>
> On Sun, 14 Jun 2009, Jan Kiszka wrote:
>
>> Blue Swirl wrote:
>>> On 6/14/09, Jan Kiszka <jan.kiszka@web.de> wrote:
>>>> [ I can't check the situation with cygwin, so this is mingw-only. ]
>>>>
>>>> gcc still does not support the Windows-specific format string modifier
>>>> "I64". Therefore, it makes no sense to check for format string
>>>> correctness and generate tons of false positives.
>>> I don't have this problem, currently mingw builds with zero warnings
>>> for me. But I didn't enable automatic -Werror flag for mingw just
>>> because I guessed this would happen. What's the gcc version you're
>>> using?
>> i686-pc-mingw32-gcc (GCC) 4.3.3
>
> 4.3.3 is known to show this bad behavior. AFAICT it is fixed in 4.4.0.
> (At least it fixed things for msysGit.)
>
> FWIW by "bad behavior" I mean that a compiler warning is emitted when
> using %I64, but not when using %ll. But when executing the program, it
> actually _requires_ a %I64, _not_ a %ll.
>
> In light of this, I _strongly_ recommend updating to 4.4.0.
I will, once I come across a pre-built one that fits. For now I'll carry
the -Wno-format as extra flags. The toolchain performs nicely otherwise.
Thanks,
Jan
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 257 bytes --]
next prev parent reply other threads:[~2009-06-15 19:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-14 18:05 [Qemu-devel] [PATCH] mingw: Do not perform string format checks Jan Kiszka
2009-06-14 18:20 ` Blue Swirl
2009-06-14 18:23 ` Jan Kiszka
2009-06-14 18:46 ` Filip Navara
2009-06-14 19:43 ` Jan Kiszka
2009-06-14 20:13 ` Johannes Schindelin
2009-06-15 19:50 ` Jan Kiszka [this message]
2009-06-15 20:25 ` Anthony Liguori
2009-06-15 22:09 ` Johannes Schindelin
2009-06-15 22:43 ` Jan Kiszka
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=4A36A60C.2000904@web.de \
--to=jan.kiszka@web.de \
--cc=Johannes.Schindelin@gmx.de \
--cc=blauwirbel@gmail.com \
--cc=qemu-devel@nongnu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.