http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52681
--- Comment #5 from Matt Kline 2012-04-18 14:04:37
UTC ---
That, if feasible, would be perfect.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52680
--- Comment #9 from Matt Kline 2012-04-17 16:35:51
UTC ---
Yes it is. Sorry for misclassifying it.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52680
--- Comment #6 from Matt Kline 2012-03-31 14:52:40
UTC ---
Well this certainly isn't my brightest moment. That seems to be the problem.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52680
--- Comment #4 from Matt Kline 2012-03-30 19:19:03
UTC ---
Where should I specify that flag? _GLIBCXX_USE_NANOSLEEP is still undefined
when I build gcc with
configure CFLAGS='-O3' --disable-bootstrap --disable-multilib
--enable-ibstdccxx-time=rt
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52680
--- Comment #2 from Matt Kline 2012-03-23 13:19:44
UTC ---
Thanks for shedding some light on this. Is there a reason that
--enable-libstdccxx-time isn't shown on
http://gcc.gnu.org/install/configure.html?
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52681
--- Comment #2 from Matt Kline 2012-03-23 13:16:23
UTC ---
Would it be possible to at least make the exception that is being thrown more
descriptive? I had guessed that some kind of compile-time warning might be
impossible, but my main concern is
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52681
Bug #: 52681
Summary: [C++11] Using std::thread without -pthread crashes
without warning
Classification: Unclassified
Product: gcc
Version: 4.7.0
Status: UNCONFIRMED
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52680
Bug #: 52680
Summary: std::this_thread::sleep_for #ifdef'd out by
_GLIBCXX_USE_NANOSLEEP
Classification: Unclassified
Product: gcc
Version: 4.7.0
Status: UNCONFIRMED
