Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/2] arch: Add support for Westmere targets
Date: Sat, 08 Jun 2019 12:08:56 +0200	[thread overview]
Message-ID: <87sgskbd8n.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20190607125313.20376-2-esben@geanix.com> (Esben Haabendal's message of "Fri, 7 Jun 2019 14:53:13 +0200")

>>>>> "Esben" == Esben Haabendal <esben@geanix.com> writes:

 > The westmere line of x86_64 targets lies between nehalem (corei7) and
 > sandybridge (corei7-avx).  Allowing use of -march=westmere enables use of AES
 > instruction set on these targets.

 > Signed-off-by: Esben Haabendal <esben@geanix.com>
 > ---
 >  arch/Config.in.x86         | 10 ++++++++++
 >  package/openblas/Config.in |  2 +-
 >  2 files changed, 11 insertions(+), 1 deletion(-)

 > diff --git a/arch/Config.in.x86 b/arch/Config.in.x86
 > index 3f6983ac1b63..26496b8d08e9 100644
 > --- a/arch/Config.in.x86
 > +++ b/arch/Config.in.x86
 > @@ -101,6 +101,15 @@ config BR2_x86_corei7
 >  	select BR2_X86_CPU_HAS_SSSE3
 >  	select BR2_X86_CPU_HAS_SSE4
 >  	select BR2_X86_CPU_HAS_SSE42
 > +config BR2_x86_westmere
 > +	bool "westmere"
 > +	select BR2_X86_CPU_HAS_MMX
 > +	select BR2_X86_CPU_HAS_SSE
 > +	select BR2_X86_CPU_HAS_SSE2
 > +	select BR2_X86_CPU_HAS_SSE3
 > +	select BR2_X86_CPU_HAS_SSSE3
 > +	select BR2_X86_CPU_HAS_SSE4
 > +	select BR2_X86_CPU_HAS_SSE42
 >  config BR2_x86_corei7_avx
 >  	bool "corei7-avx"
 >  	select BR2_X86_CPU_HAS_MMX
 > @@ -235,6 +244,7 @@ config BR2_ARCH
 >  	default "i686"		if BR2_x86_nocona && BR2_i386
 >  	default "i686"		if BR2_x86_core2 && BR2_i386
 >  	default "i686"		if BR2_x86_corei7 && BR2_i386
 > +	default "i686"		if BR2_x86_westmere && BR2_i386
 >  	default "i686"		if BR2_x86_corei7_avx && BR2_i386
 >  	default "i686"		if BR2_x86_core_avx2 && BR2_i386
 >  	default "i686"		if BR2_x86_atom && BR2_i386

No BR2_GCC_TARGET_ARCH? That doesn't seem right.

> diff --git a/package/openblas/Config.in b/package/openblas/Config.in
 > index 8e71a43f982c..c8a516bb9f93 100644
 > --- a/package/openblas/Config.in
 > +++ b/package/openblas/Config.in
 > @@ -6,7 +6,7 @@ config BR2_PACKAGE_OPENBLAS_DEFAULT_TARGET
 >  	default "PRESCOTT"     if BR2_x86_prescott || BR2_x86_nocona
 >  	default "BANIAS"       if BR2_x86_pentium_m
 >  	default "CORE2"        if BR2_x86_core2
 > -	default "NEHALEM"      if BR2_x86_corei7 || BR2_x86_silvermont
 > +	default "NEHALEM"      if BR2_x86_corei7 || BR2_x86_westmere || BR2_x86_silvermont

Please put this openblas change in a separate patch. I know we don't do
it consistently, but please sort these alphabetically - E.G. put
westmere after silvermont.

-- 
Bye, Peter Korsgaard

  reply	other threads:[~2019-06-08 10:08 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-07 12:53 [Buildroot] [PATCH 1/2] arch: Fix typo breaking use of core-avx2 arch Esben Haabendal
2019-06-07 12:53 ` [Buildroot] [PATCH 2/2] arch: Add support for Westmere targets Esben Haabendal
2019-06-08 10:08   ` Peter Korsgaard [this message]
2019-06-11  8:42     ` Esben Haabendal
2019-06-08 10:04 ` [Buildroot] [PATCH 1/2] arch: Fix typo breaking use of core-avx2 arch Peter Korsgaard
2019-06-23 19:06 ` Peter Korsgaard

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=87sgskbd8n.fsf@dell.be.48ers.dk \
    --to=peter@korsgaard.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