From: Kinsella, Ray <ray.kinsella@intel.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v4 2/2] Patch to assembler to strip LOCK prefix.
Date: Thu, 10 Sep 2015 19:54:18 +0000 [thread overview]
Message-ID: <1441914858.20486.9.camel@intel.com> (raw)
The lock prefix is usually stripped by passing to the compiler
-Wa,momit-lock-prefix=yes via EXTRA_CFLAGS. However I couldn't find
a way to get buildroot to pass CFLAGS/EXTRA_CFLAGS around.
I tried using BR2_TARGET_OPTIMIZATION, and creating a new processor type
but the flag kept stripping it out. I found the most reliable way to
achieve the behavior was to make stripping the LOCK prefix the assembler's
default behavior, hence the patch
Signed-off-by: Ray Kinsella <ray.kinsella@intel.com>
---
.../galileo/patches/binutils/2.25/default-lock-prefix.patch | 11 +++++++++++
1 file changed, 11 insertions(+)
create mode 100644 board/intel/galileo/patches/binutils/2.25/default-lock-prefix.patch
diff --git a/board/intel/galileo/patches/binutils/2.25/default-lock-prefix.patch b/board/intel/galileo/patches/binutils/2.25/default-lock-prefix.patch
new file mode 100644
index 0000000..7814ae4
--- /dev/null
+++ b/board/intel/galileo/patches/binutils/2.25/default-lock-prefix.patch
@@ -0,0 +1,11 @@
+--- a/gas/config/tc-i386.orig 2015-07-24 15:54:51.359080778 +0100
++++ b/gas/config/tc-i386.c 2015-07-24 15:54:59.692192247 +0100
+@@ -545,7 +545,7 @@ static int allow_index_reg = 0;
+
+ /* 1 if the assembler should ignore LOCK prefix, even if it was
+ specified explicitly. */
+-static int omit_lock_prefix = 0;
++static int omit_lock_prefix = 1;
+
+ static enum check_kind
+ {
--
2.1.0
reply other threads:[~2015-09-10 19:54 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1441914858.20486.9.camel@intel.com \
--to=ray.kinsella@intel.com \
--cc=buildroot@busybox.net \
/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