From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 17738 invoked by alias); 6 Oct 2005 17:01:15 -0000 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org Received: (qmail 17712 invoked by uid 48); 6 Oct 2005 17:01:09 -0000 Date: Thu, 06 Oct 2005 17:01:00 -0000 Message-ID: <20051006170109.17711.qmail@sourceware.org> X-Bugzilla-Reason: CC References: Subject: [Bug libstdc++/24196] Using string instances to pass arguments to dlls fails In-Reply-To: Reply-To: gcc-bugzilla@gcc.gnu.org To: gcc-bugs@gcc.gnu.org From: "pcarlini at suse dot de" X-SW-Source: 2005-10/txt/msg00664.txt.bz2 List-Id: ------- Comment #12 from pcarlini at suse dot de 2005-10-06 17:01 ------- I'm attaching a first draft implementing what I have in mind. Assuming testing goes well, the issue of binary compatibility should be evaluated: whereas the library-ABI is preserved, in general object code build with the current lib and with the new one will not be able to safely exchange empty strings. I don't how much this is an issue for the Cygwin project (certainly it would be for a linux distribution). Consider, anyway, that we are talking about a new configure option and those can break the binary compatibility in any way (like changing the locale model, for instance), we don't provide guarantees in those cases. We can try to figure out ways to improve that, but I'm not super confident we can make it. If binary compatibility is a major requirement, then the --enable-fully-dynamic-string option would be ok, maybe improved along the way I mentioned yesterday. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=24196