https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108673
--- Comment #4 from Christian Franke ---
I get similar results with x86_64-pc-cygwin-gcc (aka gcc) 11.3.0 and
x86_64-w64-mingw32-gcc 11.3.0, both from current Cygwin distro and with
x86_64-w64-mingw32-gcc (aka gcc) 12.2.0 from current MSYS2 dist
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108673
Christian Franke changed:
What|Removed |Added
CC||franke at computer dot org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97336
--- Comment #2 from Christian Franke ---
Sorry, but I disagree that this report is INVALID.
Unlike for example -Wstringop-overflow, warnings like -Wstring-compare should
IMO only occur if the warning condition holds for *all* function calls
gene
Component: middle-end
Assignee: unassigned at gcc dot gnu.org
Reporter: franke at computer dot org
Target Milestone: ---
Testcase:
$ uname -srvmo
CYGWIN_NT-10.0 3.1.7(0.340/5/3) 2020-08-22 17:48 x86_64 Cygwin
$ cygcheck -f /usr/bin/gcc
gcc-core-10.2.0-1
$ gcc --version
gcc (GCC
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91989
--- Comment #2 from Christian Franke ---
If the builtin is also noreturn on the other (non-x86) platforms, a cosmetic
issue remains only:
libssp/ssp.c contains dead code with a misleading comment which suggests that
__builtin_trap() may return un
Severity: normal
Priority: P3
Component: other
Assignee: unassigned at gcc dot gnu.org
Reporter: franke at computer dot org
Target Milestone: ---
Issue found in MinGW-w64 GCC 7.4.0 from current Cygwin package, but still
applies to current SVN trunk (r276567
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86138
--- Comment #25 from Christian Franke ---
(In reply to Jonathan Wakely from comment #23)
> What if you test with -D_GLIBCXX_ASSERTIONS ?
>
> (I expect you'll get a crash for either c++14 or c++17)
Yes.
Fixed with patch from r262167.
New Cygw
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86138
--- Comment #18 from Christian Franke ---
With patch from r261873, crash on -std=c++17 does no longer occur with testcase
from comment #3. Same for a wchar_t version of the testcase.
According to objdump -p, executable now imports _S_empty_rep_s
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86138
--- Comment #13 from Christian Franke ---
This patch prevents duplicate _S_empty_rep_storage[] even on Cygwin (char only,
wchar_t missing). Testcase works as expected then:
--- basic_string.tcc.orig 2018-05-03 06:22:46.0 +0200
+++
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86138
--- Comment #12 from Christian Franke ---
(In reply to Jonathan Wakely from comment #7)
> OK, so then this is the whack Windows linker model, where every DLL has its
> own address space, and probably the same as PR 81522.
Yes. Likely also affect
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86138
--- Comment #11 from Christian Franke ---
(In reply to Jonathan Wakely from comment #8)
> You still haven't explained why declaring the specialization is bogus. The
> explicit specialization is defined at
> https://gcc.gnu.org/git/?p=gcc.git;a=b
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86138
--- Comment #6 from Christian Franke ---
(In reply to Jonathan Wakely from comment #4)
> Could you please debug this to find where it's crashing and why?
It segfaults with a bogus pointer below std::string::_Rep::_M_dispose().
A comparison of as
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86138
--- Comment #5 from Christian Franke ---
(In reply to Jonathan Wakely from comment #4)
> (In reply to Christian Franke from comment #3)
> > > The extern templates are disabled because std::basic_string has additional
> > > member functions in C++
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86138
--- Comment #3 from Christian Franke ---
(In reply to Jonathan Wakely from comment #1)
> Why is the one in the DLL not compatible?
I don't know.
> The extern templates are disabled because std::basic_string has additional
> member functions in C
Severity: normal
Priority: P3
Component: libstdc++
Assignee: unassigned at gcc dot gnu.org
Reporter: franke at computer dot org
Target Milestone: ---
The function std::getline(istream &, string &, char) crashes if build with
Cygwin gcc-g++
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56747
Bug #: 56747
Summary: throw segfaults on 64bit Cygwin if -O2
(-freorder-blocks) is used with g++ 4.8.0
Classification: Unclassified
Product: gcc
Version: unknown
16 matches
Mail list logo
