From: Christian Franke <Christian.Franke@t-online.de>
To: cygwin@cygwin.com
Subject: Re: GCC 7.3.0 -std=gnu++17 failed to getline() from std::ifstream
Date: Fri, 22 Jun 2018 11:20:00 -0000 [thread overview]
Message-ID: <132567e2-8ddb-6675-1b8d-1777be1b4d99@t-online.de> (raw)
In-Reply-To: <b4f361ca-9927-c3d4-5530-2d2fd4dfd24e@t-online.de>
Christian Franke wrote:
> Marco Atzeri wrote:
>> On 6/12/2018 7:11 PM, Christian Franke wrote:
>>> ...
>>> The attached patch for
>>> /usr/lib/gcc/*-pc-cygwin/7.3.0/include/c++/bits/basic_string.h
>>> fixes this.
>>>
Please forget this patch. It was bases on a wrong assumption and only
cures symptoms.
>>
>> It seems an upstream bug so could you report it there ?
>>
>
> Done:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86138
>
If build with -std=c++17, a duplicate _S_empty_rep_storage[] which
already exists in the DLL is generated in the executable. This results
in a false negative string.empty() test in the DLL. See:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86138#c6
Workarounds:
- Link with -static, or
- Compile with -D_GLIBCXX_USE_CXX11_ABI
Fix:
https://gcc.gnu.org/viewcvs/gcc?view=revision&revision=261873
Regards,
Christian
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2018-06-22 8:49 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-05 20:32 Ivan Shynkarenka
2018-06-05 21:01 ` Marco Atzeri
2018-06-11 2:12 ` Ross Smith
2018-06-11 13:08 ` Ross Smith
2018-06-11 20:38 ` Marco Atzeri
2018-06-12 2:01 ` Ross Smith
2018-06-12 8:48 ` Ross Smith
2018-06-12 18:02 ` Christian Franke
2018-06-13 0:44 ` Ross Smith
2018-06-13 3:05 ` Ross Smith
2018-06-13 8:49 ` Marco Atzeri
2018-06-14 9:16 ` Christian Franke
2018-06-22 11:20 ` Christian Franke [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-06-05 15:56 Ivan Shynkarenka
2018-06-05 19:13 ` Hans-Bernhard Bröker
2018-06-05 20:17 ` Marco Atzeri
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=132567e2-8ddb-6675-1b8d-1777be1b4d99@t-online.de \
--to=christian.franke@t-online.de \
--cc=cygwin@cygwin.com \
/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).