Please don't use Chinese word in this mailing list, maybe somebody
need to read LKML guideline firstly.

Does this patch have many use case upon it? if there have many use
case, maybe we can worth to do it, otherwise it maybe need to
consider..., as we known, there have many person debug kernel just
using -O2 or kdb, etc...
we need to think once bring this config option, there will have so
many maintain work on it, every maintainer need to care for their
commit file to make sure the file can work with this -O0 mode.

If there have some files missed to support with the -O0 mode, the
kernel will not stable(also it have a little hard to find which
file/function cause unstable), and the unstable kernel is not
everybody want to see.

quoted text
>> +ifdef CONFIG_CC_CLOSE_OPTIMIZATION
>> +CFLAGS_process_$(BITS).o       += -O2
>> +CFLAGS_entry_$(BITS).o         += -O2
>> +CFLAGS_traps.o                 += -O2
>> +CFLAGS_i387.o                  += -O2
>> +CFLAGS_xsave.o                 += -O2
>> +CFLAGS_hpet.o                  += -O2

CONFIG_CC_CLOSE_OPTIMIZATION really misunderstand user in here with adding -O2.

   Thanks.
--
unsubscribe notice
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/