https://gcc.gnu.org/bugzilla/show_bug.cgi?id=62002
Paolo Carlini changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=62002
Vincenzo Romano changed:
What|Removed |Added
CC||vincenzo.romano at notorand
dot it
--
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=62002
--- Comment #6 from Viacheslav Chernyshev ---
Still happens on 5.3.0.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=62002
Viacheslav Chernyshev changed:
What|Removed |Added
Version|4.9.2 |5.1.0
--- Comment #5 from Viache
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=62002
--- Comment #4 from Igor Zamyatin ---
Right, it is mentioned explicitly in the docs. Will take a look
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=62002
--- Comment #3 from Viacheslav Chernyshev ---
No, fcilkplus switch triggers compilation error when code is perfectly valid.
Your example is wrong, as in C++ this pointer is an implicit first argument of
member function.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=62002
Igor Zamyatin changed:
What|Removed |Added
CC||izamyatin at gmail dot com
--- Comment #
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=62002
Marek Polacek changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
