From: Nicholas Mc Guire <der.herr@hofr.at>
To: Shawn Jin <shawnxjin@gmail.com>
Cc: ppcdev <linuxppc-dev@ozlabs.org>
Subject: Re: How to build the kernel without any optimization?
Date: Sat, 21 Aug 2010 09:31:16 +0200 [thread overview]
Message-ID: <20100821073116.GA1597@opentech.at> (raw)
In-Reply-To: <AANLkTinb9yJk10yE2nAT_exNaANHyFbAH59LOM=Jy7Oz@mail.gmail.com>
On Fri, 20 Aug 2010, Shawn Jin wrote:
> Hi,
>
> I'm tracing the execution of ds1307_probe() and find that some of
> variables or function arguments cannot be printed in gdb because they
> are optimized out or not in the current context. This really gives
> some headache. Is there a way to build the kernel without any
> optimization? What gcc option shall I disable or add?
>
> I already added the following to arch/powerpc/Makefile.
>
> # Prevent GDB from jumping around in the code when trying to single step
> ifeq ($(CONFIG_DEBUG_KERNEL),y)
> KBUILD_CFLAGS += -fno-schedule-insns -fno-schedule-insns2
> endif
>
much of the kernel can not be build without optimization - what you
can do though is slectively try to disable optimization for specific
files by putting
CFLAGS_REMOVE_objfilenam.o = -SOME_OPT
in the Makefile. I think that is safer than what you did above as this would
always depend on the order of options that ultimately get passed to gcc.
hofrat
next prev parent reply other threads:[~2010-08-21 7:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-21 6:59 How to build the kernel without any optimization? Shawn Jin
2010-08-21 7:31 ` Nicholas Mc Guire [this message]
2010-08-23 18:18 ` Shawn Jin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20100821073116.GA1597@opentech.at \
--to=der.herr@hofr.at \
--cc=linuxppc-dev@ozlabs.org \
--cc=shawnxjin@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).