From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v4 1/5] target: add symbols for i386/x86_64 cpu features
Date: Tue, 10 Jul 2012 08:11:34 +0200 [thread overview]
Message-ID: <4FFBC796.9030204@mind.be> (raw)
In-Reply-To: <1341528156-4197-2-git-send-email-s.martin49@gmail.com>
On 07/06/12 00:42, Samuel Martin wrote:
[snip]
> +config BR2_X86_CPU_HAS_SSE41
> + bool
> +config BR2_X86_CPU_HAS_SSE42
> + bool
> +config BR2_X86_CPU_HAS_SSE4
> + bool
> +config BR2_X86_CPU_HAS_SSE4A
> + bool
I don't like these SSE4 configs which are not selected by anything. I understand
that you need them for OpenCV, but it's not ideal.
Maybe we need an extra subarchitecture config option to explicitly enable these?
They should depend on core2 || barcelona, probably.
Regards,
Arnout
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286540
Essensium/Mind http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint: 7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F
next prev parent reply other threads:[~2012-07-10 6:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-05 22:42 [Buildroot] [PATCH v4 0/5] OpenCV update and CPU fetures Samuel Martin
2012-07-05 22:42 ` [Buildroot] [PATCH v4 1/5] target: add symbols for i386/x86_64 cpu features Samuel Martin
2012-07-10 6:11 ` Arnout Vandecappelle [this message]
2012-07-13 21:26 ` Thomas Petazzoni
2012-07-13 21:57 ` Samuel Martin
2012-07-13 22:46 ` Thomas Petazzoni
2012-07-05 22:42 ` [Buildroot] [PATCH v4 2/5] libevas: refactor *_CONF_OPT assignment with cpu-feature options Samuel Martin
2012-07-05 22:42 ` [Buildroot] [PATCH v4 3/5] sdl_gfx: " Samuel Martin
2012-07-05 22:42 ` [Buildroot] [PATCH v4 4/5] sdl_sound: " Samuel Martin
2012-07-05 22:42 ` [Buildroot] [PATCH v4 5/5] opencv: bump to version 2.4.1 Samuel Martin
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=4FFBC796.9030204@mind.be \
--to=arnout@mind.be \
--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 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.