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 1/3] kbuild: Fix debugging info generation for .S files
Date: Wed, 11 Dec 2013 23:34:40 +0000 [thread overview]
Message-ID: <cef1ba27f4070a4ae78c77c8d43165c48e3e6c1f.1386804405.git.geoff@infradead.org> (raw)
In-Reply-To: <cover.1386804405.git.geoff@infradead.org>
Change the debuging info generation flag in KBUILD_AFLAGS from '-gdwarf-2' to
'-Wa,--gdwarf-2'. This will properly generate the debugging info for .S files
when CONFIG_DEBUG_INFO=y.
It seems current gcc does not pass a '--gdwarf-2' option on to the assembler
when '-gdwarf-2' is on its command line (note the differece in the gcc and as
flags). This change provides the correct assembler flag to gcc, and so does
not rely on gcc to emit a flag for the assembler.
Signed-off-by: Geoff Levand <geoff@infradead.org> for Huawei, Linaro
---
Makefile | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Makefile b/Makefile
index 890392f..7308a6f 100644
--- a/Makefile
+++ b/Makefile
@@ -619,7 +619,7 @@ endif
ifdef CONFIG_DEBUG_INFO
KBUILD_CFLAGS += -g
-KBUILD_AFLAGS += -gdwarf-2
+KBUILD_AFLAGS += -Wa,--gdwarf-2
endif
ifdef CONFIG_DEBUG_INFO_REDUCED
--
1.8.1.2
next prev parent reply other threads:[~2013-12-11 23:34 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 2/3] frv: Remove redundent debugging info flag 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 ` Geoff Levand [this message]
2014-01-27 21:03 ` [PATCH 1/3] kbuild: Fix debugging info generation for .S files Michal Marek
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 ` [PATCH V2 3/3] mn10300: Remove redundant " Geoff Levand
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=cef1ba27f4070a4ae78c77c8d43165c48e3e6c1f.1386804405.git.geoff@infradead.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.