public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Adhemerval Zanella <adhemerval.zanella@linaro.org>
To: Ramana Radhakrishnan <ramana.gcc@googlemail.com>,
	Phil Blundell <pb@pbcl.net>
Cc: GNU C Library <libc-alpha@sourceware.org>
Subject: Re: [PATCH 4/4] arm: Enable ARM mode for armv6 strlen
Date: Thu, 12 Apr 2018 19:41:00 -0000	[thread overview]
Message-ID: <99d8482b-851a-fd1c-f829-f219e24d79a8@linaro.org> (raw)
In-Reply-To: <CAJA7tRahZ7L=zBs2z+zgCR=RTuccipdjBXhprjxybErebUwv1A@mail.gmail.com>



On 12/04/2018 16:32, Ramana Radhakrishnan wrote:
> 
> 
> On Thu, 12 Apr 2018, 20:28 Phil Blundell, <pb@pbcl.net <mailto:pb@pbcl.net>> wrote:
> 
>     On Thu, 2018-04-12 at 16:20 -0300, Adhemerval Zanella wrote:
>     > In fact for strlen we still require to provide a ARM only mode, since
>     > armv7 build will select this implementation as default and it still
>     > possible the user would require a ARM only build.  
> 
>     ARMv7 guarantees Thumb2 is available, doesn't it?
> 
> 
> Yep. I am puzzled as to why this patchset is.needed .
> 
> Ramana

Because as reported by BZ#23031 [1], the user is using a kernel explicit
configured to no enable thumb instructions. Although this kernel config 
is debatable whether is brings any gain to userland, it still a valid
one.

[1] https://sourceware.org/bugzilla/show_bug.cgi?id=23031

  parent reply	other threads:[~2018-04-12 19:41 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-11 21:16 [PATCH 1/4] arm: Fix armv7 neon memchr on ARM mode Adhemerval Zanella
2018-04-11 21:16 ` [PATCH 4/4] arm: Enable ARM mode for armv6 strlen Adhemerval Zanella
2018-04-11 22:12   ` Phil Blundell
2018-04-12 12:42     ` Adhemerval Zanella
2018-04-12 15:33       ` Phil Blundell
2018-04-12 16:16         ` Adhemerval Zanella
2018-04-12 19:20           ` Adhemerval Zanella
2018-04-12 19:28             ` Phil Blundell
     [not found]               ` <CAJA7tRahZ7L=zBs2z+zgCR=RTuccipdjBXhprjxybErebUwv1A@mail.gmail.com>
2018-04-12 19:41                 ` Adhemerval Zanella [this message]
2018-04-12 20:31                   ` Phil Blundell
2018-04-12 20:49                     ` Adhemerval Zanella
2018-04-13  9:56                       ` Phil Blundell
2018-04-13 11:56                         ` Adhemerval Zanella
2018-04-13 12:06                         ` Ramana Radhakrishnan
2018-04-13 12:44                           ` Phil Blundell
2018-04-13 14:40                             ` Adhemerval Zanella
2018-04-13 15:07                               ` Phil Blundell
2018-04-13 16:42                                 ` Adhemerval Zanella
2018-04-13 19:09                                   ` Phil Blundell
2018-04-13 20:12                                     ` Adhemerval Zanella
2018-04-16 14:16                                     ` Richard Earnshaw (lists)
2018-04-11 21:16 ` [PATCH 2/4] arm: Fix armv7 neon strcmp on ARM mode Adhemerval Zanella
2018-04-11 21:16 ` [PATCH 3/4] arm: Enable ARM mode for armv6 memchr Adhemerval Zanella
2018-04-13 15:10 [PATCH 4/4] arm: Enable ARM mode for armv6 strlen Wilco Dijkstra
2018-04-13 15:43 ` Wilco Dijkstra
2018-04-13 15:48   ` Florian Weimer

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=99d8482b-851a-fd1c-f829-f219e24d79a8@linaro.org \
    --to=adhemerval.zanella@linaro.org \
    --cc=libc-alpha@sourceware.org \
    --cc=pb@pbcl.net \
    --cc=ramana.gcc@googlemail.com \
    /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).