From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v1] binutils-2.27: backport patch to enable CRC instructions on supported ARMv8-A CPUs
Date: Mon, 17 Jul 2017 09:08:58 +0200 [thread overview]
Message-ID: <20170717090858.26da5867@windsurf> (raw)
In-Reply-To: <20170716233123.5652e111@gmx.net>
Hello,
On Sun, 16 Jul 2017 23:31:23 +0200, Peter Seiderer wrote:
> > Thanks for this patch. You're adding it to binutils 2.27, what about
> > binutils 2.26.1 ? The bug doesn't exist ?
>
> Bug exists with binutils 2.26.1 but the simple approach to backport (only)
> the same patch did not work:
>
> ./../include/opcode/arm.h:253:53: error: ?ARM_AEXT2_V8A? undeclared here (not in a function)
>
> Seems more patches are missing...
Argh, ok. I honestly don't think it's really worth the effort trying to
fix this specific problem on the older binutils 2.26, so let's leave
things as-is, the problem will disappear by itself once we bump to
binutils 2.29, and remove binutils 2.26.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2017-07-17 7:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-15 23:11 [Buildroot] [PATCH v1] binutils-2.27: backport patch to enable CRC instructions on supported ARMv8-A CPUs Peter Seiderer
2017-07-15 23:11 ` [Buildroot] [PATCH v1] qt5base: fix qthash error attribute(target("+crc")) is unknown Peter Seiderer
2017-07-17 21:22 ` Arnout Vandecappelle
2017-07-20 18:52 ` Peter Seiderer
2017-07-16 7:20 ` [Buildroot] [PATCH v1] binutils-2.27: backport patch to enable CRC instructions on supported ARMv8-A CPUs Thomas Petazzoni
2017-07-16 21:31 ` Peter Seiderer
2017-07-17 7:08 ` Thomas Petazzoni [this message]
2017-07-16 7:57 ` Thomas Petazzoni
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=20170717090858.26da5867@windsurf \
--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 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.