public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jsm28 at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/46908] printf not handling printing of double correctly in certain cases
Date: Mon, 13 Dec 2010 18:28:00 -0000	[thread overview]
Message-ID: <bug-46908-4-oazJpLDoTz@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-46908-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46908

Joseph S. Myers <jsm28 at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
          Component|c                           |target
         Resolution|                            |INVALID

--- Comment #6 from Joseph S. Myers <jsm28 at gcc dot gnu.org> 2010-12-13 18:28:22 UTC ---
GCC knows about the limitations of the Windows (msvcrt) printf and scanf
functions, which do not support all standard C99 formats, and the warnings are
telling you that they are not supported by those libraries.  The MinGW
libraries (wrapping msvcrt) are a separate project from GCC and there is no GCC
bug here.


      parent reply	other threads:[~2010-12-13 18:28 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-12 16:12 [Bug c/46908] New: " adrian.hawryluk at gmail dot com
2010-12-12 16:51 ` [Bug c/46908] " schwab@linux-m68k.org
2010-12-12 17:32 ` manu at gcc dot gnu.org
2010-12-12 22:53 ` adrian.hawryluk at gmail dot com
2010-12-12 22:55 ` adrian.hawryluk at gmail dot com
2010-12-12 23:09 ` adrian.hawryluk at gmail dot com
2010-12-13 18:28 ` jsm28 at gcc dot gnu.org [this message]

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-46908-4-oazJpLDoTz@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).