public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dannysmith at users dot sourceforge dot net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/37522] [4.4 regression] Incorrect vswprintf prototype breaks __to_xstring
Date: Mon, 15 Sep 2008 02:59:00 -0000 [thread overview]
Message-ID: <20080915025740.27856.qmail@sourceware.org> (raw)
In-Reply-To: <bug-37522-8837@http.gcc.gnu.org/bugzilla/>
------- Comment #1 from dannysmith at users dot sourceforge dot net 2008-09-15 02:57 -------
>
> I guess the solution is to make libstdc++ use _vsnwprintf instead of vswprintf
> on *-mingw32.
>
I think that is the most expedient solution. Would an inline redirection of
vswprintf to _vsnwprintf in config/os/mingw32/os_define.h (later, if it gets
fixed in mingw runtime that could be made conditional on mingw version) work?
Danny
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=37522
next prev parent reply other threads:[~2008-09-15 2:59 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-14 23:26 [Bug libstdc++/37522] New: " aaronavay62 at aaronwl dot com
2008-09-14 23:28 ` [Bug libstdc++/37522] " aaronavay62 at aaronwl dot com
2008-09-15 2:59 ` dannysmith at users dot sourceforge dot net [this message]
2008-09-15 17:12 ` paolo dot carlini at oracle dot com
2008-09-15 17:36 ` paolo dot carlini at oracle dot com
2008-09-16 0:16 ` aaronavay62 at aaronwl dot com
2008-09-16 0:23 ` paolo dot carlini at oracle dot com
2008-10-22 3:34 ` mmitchel at gcc dot gnu dot org
2008-10-27 10:00 ` jakub at gcc dot gnu dot org
2008-10-27 10:11 ` paolo dot carlini at oracle dot com
2008-10-27 15:03 ` paolo at gcc dot gnu dot org
2008-10-27 15:04 ` paolo dot carlini at oracle dot com
[not found] <bug-37522-4@http.gcc.gnu.org/bugzilla/>
2013-01-19 11:34 ` koala01 at free dot fr
2013-01-19 11:38 ` ktietz at gcc dot gnu.org
2013-01-19 11:47 ` koala01 at free dot fr
2013-01-19 11:53 ` ktietz at gcc dot gnu.org
2013-01-25 21:37 ` jason at gcc dot gnu.org
2013-01-25 23:54 ` ktietz at gcc dot gnu.org
2013-03-05 1:17 ` k2k at narod dot ru
2013-03-05 1:28 ` k2k at narod dot ru
2014-12-22 16:42 ` redi at gcc dot gnu.org
2015-05-28 16:28 ` redi at gcc dot gnu.org
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=20080915025740.27856.qmail@sourceware.org \
--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).