public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ptsekov at gmx dot net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/24196] Using string instances to pass arguments to dlls fails
Date: Wed, 05 Oct 2005 08:36:00 -0000 [thread overview]
Message-ID: <20051005083612.13967.qmail@sourceware.org> (raw)
In-Reply-To: <bug-24196-7246@http.gcc.gnu.org/bugzilla/>
------- Comment #5 from ptsekov at gmx dot net 2005-10-05 08:36 -------
Paolo, I guess it is obvious to anyone around that _S_empty_rep_storage is
there to speed up things. What is not obvious to Cygwin users is that this
optimization actually makes their programs crash. And let me assure you that
the crash is not easy to track down unless you want to step trough assembler
code.
Anyway, what I meant was that it may be good to have
_GLIBCXX_FULLY_DYNAMIC_STRING undefined for the common case but not for the
current libstdc++ on Cygwin i.e. libstdc++ comes as a static library. Maybe
this question concerns only Cygwin and is not of general interest and as such
should be discussed only on the Cygwin mailing list.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=24196
next prev parent reply other threads:[~2005-10-05 8:36 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-04 19:07 [Bug libstdc++/24196] New: " gerrit at gcc dot gnu dot org
2005-10-04 19:08 ` [Bug libstdc++/24196] " gerrit at gcc dot gnu dot org
2005-10-04 19:10 ` pinskia at gcc dot gnu dot org
2005-10-04 19:28 ` ptsekov at gmx dot net
2005-10-04 20:53 ` pcarlini at suse dot de
2005-10-05 8:36 ` ptsekov at gmx dot net [this message]
2005-10-05 8:51 ` pcarlini at suse dot de
2005-10-05 10:20 ` pcarlini at suse dot de
2005-10-06 11:50 ` pcarlini at suse dot de
2005-10-06 12:50 ` ptsekov at gmx dot net
2005-10-06 12:53 ` pcarlini at suse dot de
2005-10-06 17:00 ` pcarlini at suse dot de
2005-10-06 17:01 ` pcarlini at suse dot de
2005-10-07 12:13 ` ptsekov at gmx dot net
2005-10-07 17:06 ` pcarlini at suse dot de
2006-05-17 10:03 ` dave dot korn at artimi dot com
2006-05-17 10:09 ` pcarlini at suse dot de
2006-07-06 1:06 ` dannysmith at users dot sourceforge dot net
2009-04-25 19:10 ` ktietz at gcc dot gnu dot org
2009-04-25 19:17 ` paolo dot carlini at oracle dot com
2009-06-29 15:12 ` dave dot korn dot cygwin at gmail dot com
2009-10-25 5:40 ` johnw at gnu dot org
2009-10-25 5:44 ` johnw at gnu dot org
2009-10-25 5:50 ` johnw at gnu dot org
2009-10-25 5:51 ` paolo dot carlini at oracle dot com
2010-03-20 19:46 ` davek at gcc dot gnu dot org
2010-06-01 20:51 ` steven at gcc dot gnu dot org
[not found] <bug-24196-4@http.gcc.gnu.org/bugzilla/>
2014-02-16 13:12 ` jackie.rosen at hushmail dot com
2015-03-23 13:36 ` 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=20051005083612.13967.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).