From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 24277 invoked by alias); 1 Dec 2010 15:42:58 -0000 Received: (qmail 24218 invoked by uid 22791); 1 Dec 2010 15:42:56 -0000 X-SWARE-Spam-Status: No, hits=-2.7 required=5.0 tests=BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW X-Spam-Check-By: sourceware.org Received: from mail-ew0-f41.google.com (HELO mail-ew0-f41.google.com) (209.85.215.41) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Wed, 01 Dec 2010 15:42:45 +0000 Received: by ewy27 with SMTP id 27so17239632ewy.0 for ; Wed, 01 Dec 2010 07:42:42 -0800 (PST) MIME-Version: 1.0 Received: by 10.216.44.208 with SMTP id n58mr2272078web.39.1291218162653; Wed, 01 Dec 2010 07:42:42 -0800 (PST) Received: by 10.216.174.209 with HTTP; Wed, 1 Dec 2010 07:42:42 -0800 (PST) In-Reply-To: References: <20101129081619.GD5218@cr0.nay.redhat.com> <4CF36741.9000808@loongson.cn> <4CF3762B.9010102@loongson.cn> Date: Wed, 01 Dec 2010 15:42:00 -0000 Message-ID: Subject: Re: [hellogcc] Re: [PATCH] Built kernel without -O2 option From: jovi zhang To: Hui Zhu , bekars , qiaochong@loongson.cn Cc: hellogcc@freelists.org, =?UTF-8?Q?Am=C3=A9rico_Wang?= , linux-kernel@vger.kernel.org, gdb@sourceware.org Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2010-12/txt/msg00013.txt.bz2 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. >> +ifdef CONFIG_CC_CLOSE_OPTIMIZATION >> +CFLAGS_process_$(BITS).o =C2=A0 =C2=A0 =C2=A0 +=3D -O2 >> +CFLAGS_entry_$(BITS).o =C2=A0 =C2=A0 =C2=A0 =C2=A0 +=3D -O2 >> +CFLAGS_traps.o =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = +=3D -O2 >> +CFLAGS_i387.o =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0+=3D -O2 >> +CFLAGS_xsave.o =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = +=3D -O2 >> +CFLAGS_hpet.o =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0+=3D -O2 CONFIG_CC_CLOSE_OPTIMIZATION really misunderstand user in here with adding = -O2. =C2=A0 =C2=A0Thanks.