On Thu, Nov 12, 2020 at 09:41:39AM +0000, Daniel P. Berrangé wrote: Can't we have the warning disabled (maybe by force casting it before the macro or in a macro wrapper) just on those lines? Because otherwise we are silencing whole lot of other warnings that are actually very good to have, like discarding const qualifiers etc. in the rest of the code AFAIUI.

On Thu, Nov 12, 2020 at 12:48:21PM +0000, Daniel P. Berrangé wrote: I'm quite sure this flag exists for a long time already. Maybe gobject changed something lately? Also what clang version does rawhide have? With clang 11.0 and current master I'm not getting any such warning and 12.0 is still in progress. Maybe rawhide is shipping some buggy pre-release again? I'm quite sure this is very severe issue that needs to be fixed either in gobject or clang as otherwise this is a valid code that compiles without a notice: const char * meh(char **input) { char *ret = ((const char *const *)input)[0]; return ret; } int main(int argc, char **argv) { char *ptr = meh((const char *const *) argv); if (ptr[0] != '.') return 1; return 0; } And since we are at least trying to keep some C const correctness this warning might actually help us catch some of common problems. Like, for example, imagine this stupid code: void meh(const char *tmp, void *opaque) { char *data = opaque; data[0] = tmp[0]; } int main(int argc, char **argv) { const char *cnst = "asdf"; meh(cnst, argv[0]); return 0; } It works as it should and if you change the order of the arguments to the "meh" function by mistake, then the compiler will shout at you. Unless you use -Wno-incompatible-pointer-types-discards-qualifiers in which case it will compile, run, and segfault (if your system is sane). G_DEFINE_TYPE is currently used 4 times in our code. One extra cast or a wrapper macro (for the time being) is not something that tedious, especially since this needs to be dealt with in either glib or clang. Maybe the workaround is not as easy as I imagine, but I can't really try it since I'm not getting this error. Since most of these are solvable by force-casting it I don't think it's going to be that bad. I just do not like disabling warnings for no good reason. Please give the temporary workaround some thought, thank you.