[Bug c++/78920] New: libstdc++ defines a macro named "major"

2016-12-23 Thread zhouyan at me dot com
mponent: c++ Assignee: unassigned at gcc dot gnu.org Reporter: zhouyan at me dot com Target Milestone: --- Here is a minimal example, #include #ifdef major #error #endif The example check if there's a macro named "major" defined. I observed this recently when

[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

[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)

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

2014-12-15 Thread zhouyan at me dot com
Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: zhouyan at me dot com Below is a minimum example, #include int main () { std::mt19937 eng; std::normal_distribution<> rnorm; _Cilk_for (int i = 0; i != 1; ++ i)