https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93911
--- Comment #4 from Tomasz Kłoczko <kloczko.tomasz at gmail dot com> --- In this actual case it is flood of such warnings when LTO is used. Looks like glib developers are trying to tell that this those warnings should be calmed down. I know that LTO is pushing a lot of inlining so question is this correct code or not or maybe it is something which is only trying to inline such code when in reality LTO in such cases should be no trying to do that? Because that macro is part of the API it will affect more projects so if gcc is perfectly fine and it is kind of exertion which is acceptable maybe that code in glib header file should have altered that warning? I'm just looking for any hints which could improve situation here and/or encircle something which potentially can/could be corrected.
