From: Hartley Sweeten <HartleyS@visionengravers.com>
To: Alexander Sverdlin <alexander.sverdlin@gmail.com>,
Arnd Bergmann <arnd@kernel.org>
Cc: "soc@kernel.org" <soc@kernel.org>, Arnd Bergmann <arnd@arndb.de>,
Russell King <linux@armlinux.org.uk>,
Nathan Chancellor <nathan@kernel.org>,
Nick Desaulniers <ndesaulniers@google.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"clang-built-linux@googlegroups.com"
<clang-built-linux@googlegroups.com>
Subject: RE: [PATCH] ARM: ep93xx: don't use clang IAS for crunch
Date: Fri, 26 Feb 2021 19:32:42 +0000 [thread overview]
Message-ID: <BYAPR01MB5621DC2003DA49EA64AD46A0D09D9@BYAPR01MB5621.prod.exchangelabs.com> (raw)
In-Reply-To: <141f3098744ea8d1cc39abcdce89c0e513bfbc70.camel@gmail.com>
On Friday, February 26, 2021 12:23 PM, Alexander Sverdlin wrote:
> On Fri, 2021-02-26 at 17:43 +0100, Arnd Bergmann wrote:
>> Randconfig builds with ep93xx fail with the clang integrated assembler
>> that does not understand the maverick crunch extensions:
>>
>> arch/arm/mach-ep93xx/crunch-bits.S:94:2: error: invalid instruction
>> cfstr64 mvdx0, [r1, #0] @ save 64b registers
>>
>> It is unclear if anyone is still using support for crunch: gcc-4.8
>> dropped it in 2012 when it was already too broken to be used
>> reliabled. glibc support existed as an external patch but was never merged upstream.
>> We could consider removing the last bits of the kernel support as well.
>
> This was my impression already in 2006, that Cirrus is not going to work on Crunch support. From my PoV it's OK to remove the support in the kernel completely.
Martin Guy did a lot of work trying to get the maverick crunch working but I was never able to successfully use it for anything. It "kind" of works but depending on the EP93xx silicon revision there are still a number of hardware bugs that either give imprecise or garbage results.
I have no problem with removing the kernel support for the maverick crunch.
Hartley
next prev parent reply other threads:[~2021-02-26 19:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20210226164345.3889993-1-arnd@kernel.org>
2021-02-26 19:23 ` Alexander Sverdlin
2021-02-26 19:32 ` Hartley Sweeten [this message]
2021-02-26 20:47 ` Nick Desaulniers
[not found] ` <CAK8P3a2E0pv6PKzcCoRZH0G_gGrhWeiDwN7h090iQpd6c=XG1Q@mail.gmail.com>
2021-06-03 23:27 ` Nick Desaulniers
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=BYAPR01MB5621DC2003DA49EA64AD46A0D09D9@BYAPR01MB5621.prod.exchangelabs.com \
--to=hartleys@visionengravers.com \
--cc=alexander.sverdlin@gmail.com \
--cc=arnd@arndb.de \
--cc=arnd@kernel.org \
--cc=clang-built-linux@googlegroups.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.com \
--cc=soc@kernel.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
all inboxes | Powered by JetHome®