qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@web.de>
To: Filip Navara <filip.navara@gmail.com>
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: Sun, 14 Jun 2009 21:43:09 +0200	[thread overview]
Message-ID: <4A3552CD.3070703@web.de> (raw)
In-Reply-To: <5b31733c0906141146n7927cf77ga36ae0c455d501b0@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1456 bytes --]

Filip Navara wrote:
> On Sun, Jun 14, 2009 at 8:23 PM, Jan Kiszka <jan.kiszka@web.de> 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
>>
>> Jan
>>
>> JFYI, for years there was a mingw32 patch for the format strings that
> wasn't merged into the mainline gcc. It was in the MinGW patches for at
> least 4 years. Not sure if it was merged now or not..
> Best regards,
> Filip Navara
> 

Yes, I've seen the patch while looking for the reason, but I didn't read
that it is part of mingw's gcc version. Obviously, this toolchain does
not contain it. Don't know where it was derived from (hmm, mingw is
still "testing" gcc4...). I just picked what was there (for OpenSUSE) to
include a simple win32 build run in future patch development.

Well, if everyone else out there has I64 support, then I can also add
this switch to my --extra-cflags.

Jan


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 257 bytes --]

  reply	other threads:[~2009-06-14 19:43 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 [this message]
2009-06-14 20:13     ` Johannes Schindelin
2009-06-15 19:50       ` Jan Kiszka
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=4A3552CD.3070703@web.de \
    --to=jan.kiszka@web.de \
    --cc=blauwirbel@gmail.com \
    --cc=filip.navara@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 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 NNTP newsgroup(s).