From: Will Newton <will.newton@linaro.org>
To: "Joseph S. Myers" <joseph@codesourcery.com>
Cc: libc-ports@sourceware.org, Patch Tracking <patches@linaro.org>
Subject: Re: [PATCH, v5] ARM: Add Cortex-A15 optimized NEON and VFP memcpy routines, with IFUNC.
Date: Wed, 01 May 2013 09:11:00 -0000 [thread overview]
Message-ID: <CANu=DmjShQHKkqP_HXEOY5LhbcJJ4Hw1suXroM2yy9UeSJDFtw@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.64.1304301705500.21969@digraph.polyomino.org.uk>
On 30 April 2013 18:07, Joseph S. Myers <joseph@codesourcery.com> wrote:
> On Tue, 30 Apr 2013, Will Newton wrote:
>
>> * sysdeps/arm/configure.in: Require binutils 2.21 to build
>> for armv7.
>
> * sysdeps/arm/configure: Regenerated.
I added that to the changelog, but the actual change to configure is
still omitted from the patch.
>> +# If we are configuring for armv7 we need binutils 2.21 to ensure that
>> +# NEON alignments are assembled correctly.
>> +if test $machine = arm/armv7; then
>> + AC_CHECK_PROG_VER(AS, $AS, --version,
>> + [GNU assembler.* \([0-9]*\.[0-9.]*\)],
>> + [2.1[0-9][0-9]*|2.[2-9][1-9]*|[3-9].*|[1-9][0-9]*], AS=: critic_missing="$critic_missing as")
>
> That looks like it would reject versions 2.30, 2.40, ... - and does this
> run early enough for the critic_missing setting to be effective?
No, you're right. I've fixed up the error handling and the glob.
--
Will Newton
Toolchain Working Group, Linaro
next prev parent reply other threads:[~2013-05-01 9:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-30 16:54 Will Newton
2013-04-30 17:08 ` Joseph S. Myers
2013-05-01 9:11 ` Will Newton [this message]
2013-04-30 17:18 ` Roland McGrath
2013-05-01 15:26 ` Will Newton
2013-05-01 17:01 ` Roland McGrath
2013-05-01 18:43 ` Will Newton
2013-05-02 19:54 ` Roland McGrath
2013-05-01 12:53 ` Richard Henderson
2013-05-01 16:50 ` Roland McGrath
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='CANu=DmjShQHKkqP_HXEOY5LhbcJJ4Hw1suXroM2yy9UeSJDFtw@mail.gmail.com' \
--to=will.newton@linaro.org \
--cc=joseph@codesourcery.com \
--cc=libc-ports@sourceware.org \
--cc=patches@linaro.org \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).