https://gcc.gnu.org/bugzilla/show_bug.cgi?id=57440
Kai Tietz changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=57440
--- Comment #18 from Kai Tietz ---
Author: ktietz
Date: Tue Oct 14 17:06:27 2014
New Revision: 216213
URL: https://gcc.gnu.org/viewcvs?rev=216213&root=gcc&view=rev
Log:
PR libstdc++/57440
* config/os/mingw32/os_defines.h (_GTHREAD_USE_MU
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=57440
--- Comment #17 from Kai Tietz ---
Author: ktietz
Date: Tue Oct 14 17:05:04 2014
New Revision: 216212
URL: https://gcc.gnu.org/viewcvs?rev=216212&root=gcc&view=rev
Log:
PR libstdc++/57440
* config/os/mingw32/os_defines.h (_GTHREAD_USE_MU
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=57440
--- Comment #16 from Kai Tietz ---
Author: ktietz
Date: Tue Oct 14 16:58:37 2014
New Revision: 216210
URL: https://gcc.gnu.org/viewcvs?rev=216210&root=gcc&view=rev
Log:
2014-10-14 Kai Tietz
PR libstdc++/57440
* config/os/ming
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=57440
--- Comment #15 from Kai Tietz ---
Posted patch to ML for defining _GTHREAD_USE_MUTEX_INIT_FUNC in mingw-w64, and
mingw32 case. It is true that posix-threading support for Windows is right now
only provided by mingw-w64 based toolchains, neverth
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=57440
Kai Tietz changed:
What|Removed |Added
CC||ahanins at gmail dot com
--- Comment #14 fro
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=57440
--- Comment #13 from Jonathan Wakely ---
dup of PR 59807
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57440
--- Comment #12 from Jonathan Wakely ---
Using Qt Creator I have confirmed the leak, and can reproduce it with this
#include
#include
int main()
{
for (int i=0; i < 10; ++i) {
pthread_mutex_t mx = PTHREAD_MUTEX_INITIALIZER;
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57440
Jonathan Wakely changed:
What|Removed |Added
Target||i686-w64-mingw32
Status|WAI
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57440
--- Comment #10 from DrD ---
(In reply to Jonathan Wakely from comment #7)
> You didn't answer the question about which mingw compiler you are using, the
> standard mingw gcc does not support std::async.
>From my first post:
"I compile it with gc
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57440
--- Comment #9 from Jonathan Wakely ---
Some other detail. I don't care about Qt Creator, it's not a compiler, and the
version of Qt is compeltely irrelevant because you're not using Qt.
I don't believe you can be using Mingw 4.7.2, because that
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57440
--- Comment #8 from DrD ---
(In reply to Jonathan Wakely from comment #7)
> You didn't answer the question about which mingw compiler you are using, the
> standard mingw gcc does not support std::async.
>From my first post:
"I compile it with gcc
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57440
--- Comment #7 from Jonathan Wakely ---
You didn't answer the question about which mingw compiler you are using, the
standard mingw gcc does not support std::async.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57440
--- Comment #6 from DrD ---
(In reply to Jonathan Wakely from comment #4)
> If my guess is right you should be able to reproduce the unbounded memory
> usage with this:
>
> #include
>
> int f() { return 0; }
>
> int main()
> {
> for (int i
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57440
--- Comment #5 from DrD ---
(In reply to Jonathan Wakely from comment #3)
> Also I can't reproduce this on GNU/Linux, the memory usage is bounded as
> expected.
>
> I'm surprised this even compiles with Mingw, are you using Mingw-w64 with
> libpt
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57440
--- Comment #4 from Jonathan Wakely ---
If my guess is right you should be able to reproduce the unbounded memory usage
with this:
#include
int f() { return 0; }
int main()
{
for (int i=0; i < 10; ++i)
std::async(f).get();
}
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57440
Jonathan Wakely changed:
What|Removed |Added
Status|UNCONFIRMED |WAITING
Last reconfirmed|
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57440
--- Comment #3 from Jonathan Wakely ---
Also I can't reproduce this on GNU/Linux, the memory usage is bounded as
expected.
I'm surprised this even compiles with Mingw, are you using Mingw-w64 with
libpthread-win32? Since it seems to be platform-
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57440
--- Comment #2 from DrD ---
(In reply to Jonathan Wakely from comment #1)
> (In reply to DrD from comment #0)
> > // ... launch the threads
> > vector > values;
> > for (uint w=0; w > values.push_back(std::async
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57440
--- Comment #1 from Jonathan Wakely ---
(In reply to DrD from comment #0)
> // ... launch the threads
> vector > values;
> for (uint w=0; w values.push_back(std::async(TestFutures));
> }
One quick comme
20 matches
Mail list logo
