From: Saul Wold <sgw@linux.intel.com>
To: openembedded-core@lists.openembedded.org,
richard.purdie@linuxfoundation.org
Cc: dvhart@linux.intel.com
Subject: [PATCH] tune-i586-nlp: Add new tune file to support Quark/X1000 CPU
Date: Mon, 29 Jun 2015 07:10:50 -0700 [thread overview]
Message-ID: <1435587050-18517-1-git-send-email-sgw@linux.intel.com> (raw)
This tune file is needed to enable a GAS option specific to this cpu family
in order to disable the usage of lock prefix instructions.
Signed-off-by: Saul Wold <sgw@linux.intel.com>
---
meta/conf/machine/include/tune-i586-nlp.inc | 19 +++++++++++++++++++++++++++++
1 file changed, 19 insertions(+)
create mode 100644 meta/conf/machine/include/tune-i586-nlp.inc
diff --git a/meta/conf/machine/include/tune-i586-nlp.inc b/meta/conf/machine/include/tune-i586-nlp.inc
new file mode 100644
index 0000000..94e22c1
--- /dev/null
+++ b/meta/conf/machine/include/tune-i586-nlp.inc
@@ -0,0 +1,19 @@
+# Settings for the GCC(1) cpu-type "quark":
+#
+#
+#
+DEFAULTTUNE ?= "i586-nlp-32"
+
+# Include the previous tune to pull in PACKAGE_EXTRA_ARCHS
+require conf/machine/include/x86/arch-x86.inc
+
+# x86 with no lock prefix
+TUNEVALID[i586-nlp] = "IA32 with Lock Prefix omitted"
+TUNE_CCARGS .= "${@bb.utils.contains("TUNE_FEATURES", "i586-nlp", " -march=i586 -Wa,-momit-lock-prefix=yes", "", d)}"
+
+# Quark tune feature
+AVAILTUNES = "i586-nlp-32"
+TUNE_FEATURES_tune-i586-nlp-32 = "${TUNE_FEATURES_tune-x86} i586-nlp"
+BASE_LIB_tune-i586-nlp-32 = "lib"
+TUNE_PKGARCH_tune-i586-nlp-32 = "i586-nlp-32"
+PACKAGE_EXTRA_ARCHS_tune-i586-nlp-32 = "i586-nlp-32"
--
2.1.0
next reply other threads:[~2015-06-29 14:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-29 14:10 Saul Wold [this message]
2015-07-01 16:03 ` [PATCH] tune-i586-nlp: Add new tune file to support Quark/X1000 CPU Darren Hart
2015-07-02 15:53 ` Richard Purdie
-- strict thread matches above, loose matches on Subject: below --
2015-06-23 15:22 Saul Wold
2015-06-23 16:02 ` Richard Purdie
2015-06-23 17:17 ` Darren Hart
2015-06-23 17:19 ` Phil Blundell
2015-06-24 15:10 ` Darren Hart
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=1435587050-18517-1-git-send-email-sgw@linux.intel.com \
--to=sgw@linux.intel.com \
--cc=dvhart@linux.intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.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 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.