https://gcc.gnu.org/bugzilla/show_bug.cgi?id=60258
Paolo Carlini paolo.carlini at oracle dot com changed:
What|Removed |Added
Status|NEW |RESOLVED
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60258
Jonathan Wakely redi at gcc dot gnu.org changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60258
Jakub Jelinek jakub at gcc dot gnu.org changed:
What|Removed |Added
CC||jakub at gcc dot
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60258
--- Comment #2 from ja.gcc.bugzilla at aptsketch dot com ---
auto foo() - void
vs
void foo()
is more of just a stylistic issue. There is nothing wrong with both. To me both
are good.
The bug is about std::atomic member initialization. Where if
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60258
--- Comment #3 from Jakub Jelinek jakub at gcc dot gnu.org ---
Sure, my comment was about this stylistic issue, not about the real bug (if
any, haven't tried it). Note your testcase isn't self-contained, you probably
need #include atomic.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60258
Daniel Krügler daniel.kruegler at googlemail dot com changed:
What|Removed |Added
CC|
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60258
--- Comment #5 from Daniel Krügler daniel.kruegler at googlemail dot com ---
(In reply to Daniel Krügler from comment #4)
Reduced example:
More reduced by eliminating library dependencies:
//--
struct atomic_bool
{
