https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89729
--- Comment #3 from Xavier <chantry.xavier at gmail dot com> --- (In reply to Martin Sebor from comment #1) Thanks a lot for the detailed explanation, it's much clearer now. Wclass-memaccess does look sane. script_data_t is apparently manipulated from both C and C++ code, which might explain why it's done this way. We can either disable the warning in this case or use a (void *) so no problem. (In reply to Jonathan Wakely from comment #2) > You should use the gcc-help mailing list for questions like this, because > you're not reporting a bug. You're right, sorry about that.
