[Bug c++/86306] Initializing atomic qualified type with another atomic qualified type leads to assertion failure

2018-06-25 Thread graham.stott at btinternet dot com
) To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/86306] Initializing atomic qualified type with another atomic qualified type leads to assertion failure https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86306 --- Comment #9 from zhonghao at pku dot org.cn --- (In reply to zhonghao from comment #8) &

[Bug c++/86306] Initializing atomic qualified type with another atomic qualified type leads to assertion failure

2018-06-25 Thread zhonghao at pku dot org.cn
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86306 --- Comment #9 from zhonghao at pku dot org.cn --- (In reply to zhonghao from comment #8) > (In reply to Jonathan Wakely from comment #7) > > (In reply to Jonathan Wakely from comment #6) > > > Because you are just blindly copying things from one

[Bug c++/86306] Initializing atomic qualified type with another atomic qualified type leads to assertion failure

2018-06-25 Thread zhonghao at pku dot org.cn
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86306 --- Comment #8 from zhonghao at pku dot org.cn --- (In reply to Jonathan Wakely from comment #7) > (In reply to Jonathan Wakely from comment #6) > > Because you are just blindly copying things from one bugzilla to the other, > > without making

[Bug c++/86306] Initializing atomic qualified type with another atomic qualified type leads to assertion failure

2018-06-25 Thread redi at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86306 --- Comment #7 from Jonathan Wakely --- (In reply to Jonathan Wakely from comment #6) > Because you are just blindly copying things from one bugzilla to the other, > without making any effort to check if what you are reporting is sensible. For

[Bug c++/86306] Initializing atomic qualified type with another atomic qualified type leads to assertion failure

2018-06-25 Thread redi at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86306 --- Comment #6 from Jonathan Wakely --- (In reply to zhonghao from comment #5) > Another bug report (https://bugs.llvm.org/show_bug.cgi?id=21835) also used > the code. In particular, David Majnemer said that the following code, > > typedef

[Bug c++/86306] Initializing atomic qualified type with another atomic qualified type leads to assertion failure

2018-06-25 Thread zhonghao at pku dot org.cn
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86306 --- Comment #5 from zhonghao at pku dot org.cn --- (In reply to Jonathan Wakely from comment #4) > _Atomic is a C keyword, it is not part of C++. > > Clang++ accepts it as a non-standard extension. GCC ddoes not accept it, > because it's not

[Bug c++/86306] Initializing atomic qualified type with another atomic qualified type leads to assertion failure

2018-06-25 Thread redi at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86306 --- Comment #4 from Jonathan Wakely --- _Atomic is a C keyword, it is not part of C++. Clang++ accepts it as a non-standard extension. GCC ddoes not accept it, because it's not part of C++. If you don't understand what this means, stop filing

[Bug c++/86306] Initializing atomic qualified type with another atomic qualified type leads to assertion failure

2018-06-25 Thread redi at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86306 --- Comment #3 from Jonathan Wakely --- No.

[Bug c++/86306] Initializing atomic qualified type with another atomic qualified type leads to assertion failure

2018-06-25 Thread zhonghao at pku dot org.cn
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86306 --- Comment #2 from zhonghao at pku dot org.cn --- (In reply to Jonathan Wakely from comment #1) > It's correctly rejected by GCC because _Atomic is a C keyword, not a C++ one. > > Please try to understand the code before filing bugs, and

[Bug c++/86306] Initializing atomic qualified type with another atomic qualified type leads to assertion failure

2018-06-25 Thread redi at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86306 Jonathan Wakely changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|---