From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] mpir: fix ARM, PowerPC and mips builds failure
Date: Sun, 7 May 2017 21:38:54 +0200 [thread overview]
Message-ID: <20170507213854.413cfc6c@free-electrons.com> (raw)
In-Reply-To: <1494178984-19821-2-git-send-email-semenak94@mail.ru>
Hello,
On Sun, 7 May 2017 20:43:04 +0300, Semyon Kolganov wrote:
> +# Prefer generic build
> +MPIR_CONF_ENV += MPN_PATH=generic
I think this is really wrong, because it will use in all cases the
non-optimized generic code, instead of the more optimized assembly code
available for a number of architectures:
$ ls mpn/
alpha arm asm-defs.m4 cpp-ccas generic ia64 m4-ccas Makeasm.am Makefile.am Makefile.in mips32 mips64 powerpc32 powerpc64 README sparc32 sparc64 x86 x86_64 x86_64w x86w
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
prev parent reply other threads:[~2017-05-07 19:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mpir: fix ARM, PowerPC64 and MIPS build failure>
2017-05-07 17:43 ` [Buildroot] [PATCH] mpir: fix ARM, PowerPC and mips builds failure Semyon Kolganov
2017-05-07 17:43 ` Semyon Kolganov
2017-05-07 19:38 ` Thomas Petazzoni [this message]
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=20170507213854.413cfc6c@free-electrons.com \
--to=thomas.petazzoni@free-electrons.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