https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70932
--- Comment #10 from Paul Wankadia ---
(In reply to Martin Sebor from comment #9)
> Sorry, I haven't gotten to it yet.
Was this bug fixed in GCC 7.x? :)
I ask because the workaround in RE2 is conditioned thus:
#if !defined(__clang__) && define
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70932
Paul Wankadia changed:
What|Removed |Added
CC||junyer at google dot com
--- Comment #3
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70932
--- Comment #4 from Paul Wankadia ---
FWIW, using a simplified struct, Compiler Explorer (gcc.godbolt.org) with GCC
6.1 throws a different error:
#include
struct State {
int i;
std::atomic next_[];
};
Compiler output — x86 gcc 6.1 (g++
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71147
Paul Wankadia changed:
What|Removed |Added
CC||junyer at google dot com
--- Comment #8
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70932
--- Comment #7 from Paul Wankadia ---
Ahh. Thank you for clarifying. I will continue to watch this bug then. :)
