Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v3] arch: add support for "jaguar" AMD CPU optimisations.
Date: Tue, 14 Jan 2014 18:06:23 +0100	[thread overview]
Message-ID: <52D56E8F.3000100@mind.be> (raw)
In-Reply-To: <828938079.582663.1389643754921.JavaMail.root@mail>

On 13/01/14 21:09, Adrien B?raud wrote:
> AMD Jaguar (https://en.wikipedia.org/wiki/Jaguar_%28microarchitecture%29  ) is suddenly
> a popular architecture since it is used in the PS4 and the XBox One.
> Many embedded systems are also likely to use it in the next years.
>
> This patch adds support for GCC architecture-specific optimizations and tuning for these CPUs.
> These optimizations are available with GCC 4.8+.

  You'll also need to update the dependencies of 
BR2_TOOLCHAIN_EXTERNAL_CODESOURCERY_X86_*


  Regards,
  Arnout

>
> Signed-off-by: Adrien Beraud<adrien.beraud@savoirfairelinux.com>

[snip]
-- 
Arnout Vandecappelle                          arnout at mind be
Senior Embedded Software Architect            +32-16-286500
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

  reply	other threads:[~2014-01-14 17:06 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1368377135.187677.1389630463088.JavaMail.root@mail>
2014-01-13 16:37 ` [Buildroot] [PATCH] arch: add support for "jaguar" AMD CPU optimisations Adrien Béraud
2014-01-13 17:07   ` Adrien Béraud
2014-01-13 18:05     ` Yann E. MORIN
2014-01-13 18:11     ` [Buildroot] [PATCH v2] " Adrien Béraud
2014-01-13 20:09       ` [Buildroot] [PATCH v3] " Adrien Béraud
2014-01-14 17:06         ` Arnout Vandecappelle [this message]
2014-01-15 16:20         ` [Buildroot] [PATCH v4] " Adrien Béraud
2014-01-15 20:40           ` 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=52D56E8F.3000100@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox