This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug c++/64318] Using _Cilk_for with <random> cause strange floating point exception
- From: "jakub at gcc dot gnu.org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Mon, 15 Dec 2014 19:19:49 +0000
- Subject: [Bug c++/64318] Using _Cilk_for with <random> cause strange floating point exception
- Auto-submitted: auto-generated
- References: <bug-64318-4 at http dot gcc dot gnu dot org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64318
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jakub at gcc dot gnu.org,
| |redi at gcc dot gnu.org
--- Comment #2 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Are the std::mt19937 and std::normal_distribution<> classes meant to be
thread-safe? I mean, in your testcase you access (supposedly read and write)
the same objects from multiple threads, so unless the standard says it is
required to work in a thread-safe, your testcase is racy.