mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Tim Abbott <tabbott@ksplice.com>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: linux-kernel@vger.kernel.org, Tim Abbott <tabbott@ksplice.com>,
	Sam Ravnborg <sam@ravnborg.org>
Subject: [PATCH v4 1/4] kbuild: Don't define ALIGN and ENTRY when preprocessing linker scripts.
Date: Sun, 20 Sep 2009 18:14:12 -0400	[thread overview]
Message-ID: <1253484855-8067-2-git-send-email-tabbott@ksplice.com> (raw)
In-Reply-To: <1253484855-8067-1-git-send-email-tabbott@ksplice.com>

Adding a reference to <linux/linkage.h> to x86's <asm/cache.h> causes
the x86 linker script to have syntax errors, because the ALIGN and
ENTRY keywords get redefined to the assembly implementations of those.
One could fix this by adjusting the include structure, but I think any
solution based on that approach would be fragile.

Currently, it is impossible when writing a header to do something
different for assembly files and linker scripts, even though there are
clearly cases where one wants them to define macros differently for
the two (ENTRY being an excellent example).  So I think the right
solution here is to introduce a new preprocessor definition,
tentatively called LINKER_SCRIPT that is set along with __ASSEMBLY__
for linker scripts, and to use that to not define ALIGN and ENTRY in
linker scripts.  I suspect we'll find other uses for this mechanism in
the future.

Signed-off-by: Tim Abbott <tabbott@ksplice.com>
Cc: Sam Ravnborg <sam@ravnborg.org>
---
 include/linux/linkage.h |    2 ++
 scripts/Makefile.build  |    2 +-
 2 files changed, 3 insertions(+), 1 deletions(-)

diff --git a/include/linux/linkage.h b/include/linux/linkage.h
index 691f591..5126cce 100644
--- a/include/linux/linkage.h
+++ b/include/linux/linkage.h
@@ -57,6 +57,7 @@
 
 #ifdef __ASSEMBLY__
 
+#ifndef LINKER_SCRIPT
 #define ALIGN __ALIGN
 #define ALIGN_STR __ALIGN_STR
 
@@ -66,6 +67,7 @@
   ALIGN; \
   name:
 #endif
+#endif /* LINKER_SCRIPT */
 
 #ifndef WEAK
 #define WEAK(name)	   \
diff --git a/scripts/Makefile.build b/scripts/Makefile.build
index d542566..341b589 100644
--- a/scripts/Makefile.build
+++ b/scripts/Makefile.build
@@ -271,7 +271,7 @@ targets += $(extra-y) $(MAKECMDGOALS) $(always)
 # ---------------------------------------------------------------------------
 quiet_cmd_cpp_lds_S = LDS     $@
       cmd_cpp_lds_S = $(CPP) $(cpp_flags) -P -C -U$(ARCH) \
-	                     -D__ASSEMBLY__ -o $@ $<
+	                     -D__ASSEMBLY__ -DLINKER_SCRIPT -o $@ $<
 
 $(obj)/%.lds: $(src)/%.lds.S FORCE
 	$(call if_changed_dep,cpp_lds_S)
-- 
1.6.3.3


  reply	other threads:[~2009-09-20 22:14 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-20 22:14 [PATCH v4 0/4] Use macros rather than hardcoding section names Tim Abbott
2009-09-20 22:14 ` Tim Abbott [this message]
2009-09-20 22:14 ` [PATCH v4 2/4] Use new __init_task_data macro in arch init_task.c files Tim Abbott
2009-09-20 22:14 ` [PATCH v4 3/4] Use macros for .bss.page_aligned section Tim Abbott
2009-09-20 22:14 ` [PATCH v4 4/4] Use macros for .data.page_aligned section Tim Abbott
2009-09-21 23:46   ` Benjamin Herrenschmidt
2009-09-22  4:45     ` Sam Ravnborg
2009-09-22  7:10       ` Benjamin Herrenschmidt
2009-09-22 17:34     ` H. Peter Anvin
2009-09-21  4:25 ` [PATCH v4 0/4] Use macros rather than hardcoding section names Sam Ravnborg

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=1253484855-8067-2-git-send-email-tabbott@ksplice.com \
    --to=tabbott@ksplice.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sam@ravnborg.org \
    /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

Powered by JetHome