> Err - Optimization also lists it in some -help section? It's a Warning > option and certainly we don't handle per-function Warnings in general > (with LTO) even though we have #pragma GCC diagnostic, no? > > I'm not sure why we force warn_inline to zero with -O0, it seems much > better to guard false warnings in some other way for -O0?
Well, we can do that with warn_inline, but in general we do want to stream late warnings (so things like -Wmaybe-uninitialized works sort of as expected for -flto). So I guess we want way to mark option as part of TARGET_OPTIMIZATION_NODE even though it is not realy an optimization option but parameter, warning or semantic change. Honza
