[Bug middle-end/110194] GCC shouldn't warn for inline functions when -g provided.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110194 Jakub Jelinek changed: What|Removed |Added CC||jakub at gcc dot gnu.org --- Comment #6 from Jakub Jelinek --- That is complete misunderstanding on what -Winline is about. You ask the compiler to tell you when some function marked inline is not actually inlined. That is nothing generally bad or good, it is an information you asked the compiler to emit and it emitted it. If you don't want that information, don't use -Winline.
[Bug middle-end/110194] GCC shouldn't warn for inline functions when -g provided.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110194 --- Comment #5 from Umesh Kalappa --- Ok thank you @Jakub and @Andrew for the quick reply , >>-Winline Option triggers this diagnostic ,so it better not to use this option in the debug build ?
[Bug middle-end/110194] GCC shouldn't warn for inline functions when -G provided.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110194 --- Comment #4 from Jakub Jelinek --- Note, I think -Og only does early inlining and not IPA inlining, so it will inline far fewer functions than -O1, -O2, -Os etc.
[Bug middle-end/110194] GCC shouldn't warn for inline functions when -G provided.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110194 --- Comment #3 from Andrew Pinski --- Also -G and -g are different options. I was thinking you saying gcc should not warn when you specify the small data size on some targets (-G). Oh -g is independent from optimization level too.
[Bug middle-end/110194] GCC shouldn't warn for inline functions when -G provided.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110194 Andrew Pinski changed: What|Removed |Added Resolution|--- |INVALID Status|UNCONFIRMED |RESOLVED Component|c |middle-end Keywords||diagnostic --- Comment #2 from Andrew Pinski --- -Winline is working as designed and documented. There is nothing wrong here.
