From: Geoff Levand <geoff@infradead.org>
To: Michal Marek <mmarek@suse.cz>
Cc: linux-kbuild@vger.kernel.org, David Howells <dhowells@redhat.com>
Subject: [PATCH V2 3/3] mn10300: Remove redundant debugging info flag
Date: Mon, 27 Jan 2014 17:48:47 -0800 [thread overview]
Message-ID: <1390873727.5027.56.camel@smoke> (raw)
In-Reply-To: <52E6CAD7.2020208@suse.cz>
The generic makefile now sets '-Wa,--gdwarf2' in KBUILD_AFLAGS, so
this setting is no longer needed in arch makefiles.
Also remove a commented out addition of a -O1 to KBUILD_CFLAGS, and
comment text relating to these removed lines.
Cc: David Howells <dhowells@redhat.com>
Signed-off-by: Geoff Levand <geoff@infradead.org> for Huawei, Linaro
---
v2: Removed unused CONFIG_DEBUG_INFO conditional and related text comment.
arch/mn10300/Makefile | 8 --------
1 file changed, 8 deletions(-)
diff --git a/arch/mn10300/Makefile b/arch/mn10300/Makefile
index a3d0fef..3f1ea5d 100644
--- a/arch/mn10300/Makefile
+++ b/arch/mn10300/Makefile
@@ -92,14 +92,6 @@ define archhelp
echo '* zImage - Compressed kernel image (arch/$(ARCH)/boot/zImage)'
endef
-# If you make sure the .S files get compiled with debug info,
-# uncomment the following to disable optimisations
-# that are unhelpful whilst debugging.
-ifdef CONFIG_DEBUG_INFO
-#KBUILD_CFLAGS += -O1
-KBUILD_AFLAGS += -Wa,--gdwarf2
-endif
-
#
# include the appropriate processor- and unit-specific headers
#
--
1.8.1.2
next prev parent reply other threads:[~2014-01-28 1:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-11 23:34 [PATCH 0/3] Fix debugging info for .S files Geoff Levand
2013-12-11 23:34 ` [PATCH 3/3] mn10300: Remove redundent debugging info flag Geoff Levand
2014-01-27 21:08 ` Michal Marek
2014-01-28 1:48 ` Geoff Levand [this message]
2013-12-11 23:34 ` [PATCH 2/3] frv: " Geoff Levand
2014-01-28 1:48 ` [PATCH V2 2/3] frv: Remove redundant " Geoff Levand
2014-01-28 10:16 ` Michal Marek
2013-12-11 23:34 ` [PATCH 1/3] kbuild: Fix debugging info generation for .S files Geoff Levand
2014-01-27 21:03 ` Michal Marek
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=1390873727.5027.56.camel@smoke \
--to=geoff@infradead.org \
--cc=dhowells@redhat.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=mmarek@suse.cz \
/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