[Bug c++/64318] Using _Cilk_for with cause strange floating point exception

2017-12-04 Thread paolo.carlini at oracle dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64318 Paolo Carlini changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|---

[Bug c++/64318] Using _Cilk_for with cause strange floating point exception

2014-12-15 Thread redi at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64318 --- Comment #5 from Jonathan Wakely --- The original testcase does indeed have a data race. The revised testcase is valid.

[Bug c++/64318] Using _Cilk_for with cause strange floating point exception

2014-12-15 Thread zhouyan at me dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64318 --- Comment #4 from zhouyan at me dot com --- The new example can be unsafe, if the constructor of the two classes are unsafe. However, I went through the source of before (during 4.8, 4.9 release), unless something changed, it's not the case.

[Bug c++/64318] Using _Cilk_for with cause strange floating point exception

2014-12-15 Thread zhouyan at me dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64318 --- Comment #3 from zhouyan at me dot com --- Here is version that shall be thread-safe, that produce the same problem, #include int main () { _Cilk_for (int i = 0; i != 1; ++i) { std::mt19937 eng(i); std::normal_distrib

[Bug c++/64318] Using _Cilk_for with cause strange floating point exception

2014-12-15 Thread jakub at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64318 Jakub Jelinek changed: What|Removed |Added CC||jakub at gcc dot gnu.org,

[Bug c++/64318] Using _Cilk_for with cause strange floating point exception

2014-12-15 Thread zhouyan at me dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64318 --- Comment #1 from zhouyan at me dot com --- I forgot to mention that, the system is CentOS 7 (with all updates)