From: David Woodhouse <dwmw2@infradead.org>
To: hpa@zytor.com
Cc: mingo@kernel.org, tglx@linutronix.de, linux-kernel@vger.kernel.org
Subject: [PATCH] x86/boot: use .code16 instead of .code16gcc
Date: Fri, 03 Jan 2014 22:30:42 +0000 [thread overview]
Message-ID: <1388788242.2391.75.camel@shinybook.infradead.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1231 bytes --]
This reverts commit 28b48688 ("x86, boot: use .code16gcc instead
of .code16").
Versions of binutils older than 2.16 are already not working, so this
workaround is no longer necessary either.
Signed-off-by: David Woodhouse <David.Woodhouse@intel.com>
---
Since I just made .code16 work in LLVM, this removes one more barrier to
building the kernel with LLVM/clang. And it looks like 'clang -m16' for
the C code in arch/x86/boot shouldn't actually be that hard to do now
either.
diff --git a/arch/x86/boot/bioscall.S b/arch/x86/boot/bioscall.S
index 1dfbf64..5077937 100644
--- a/arch/x86/boot/bioscall.S
+++ b/arch/x86/boot/bioscall.S
@@ -13,7 +13,7 @@
* touching registers they shouldn't be.
*/
- .code16gcc
+ .code16
.text
.globl intcall
.type intcall, @function
diff --git a/arch/x86/boot/copy.S b/arch/x86/boot/copy.S
index 11f272c..07a7a4a 100644
--- a/arch/x86/boot/copy.S
+++ b/arch/x86/boot/copy.S
@@ -14,7 +14,7 @@
* Memory copy routines
*/
- .code16gcc
+ .code16
.text
GLOBAL(memcpy)
--
David Woodhouse Open Source Technology Centre
David.Woodhouse@intel.com Intel Corporation
--
dwmw2
[-- Attachment #2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 5745 bytes --]
next reply other threads:[~2014-01-03 22:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-03 22:30 David Woodhouse [this message]
2014-01-03 22:34 ` H. Peter Anvin
2014-01-03 23:12 ` David Woodhouse
2014-01-03 23:18 ` H. Peter Anvin
2014-01-03 22:46 ` [tip:x86/build] x86, boot: Use " tip-bot for David Woodhouse
2014-01-04 22:04 ` tip-bot for David Woodhouse
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=1388788242.2391.75.camel@shinybook.infradead.org \
--to=dwmw2@infradead.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=tglx@linutronix.de \
/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
all inboxes | Powered by JetHome®