From: Martin Guy <martinwguy@gmail.com> To: Arnd Bergmann <arnd@kernel.org> Cc: Russell King <linux@armlinux.org.uk>, Hartley Sweeten <hsweeten@visionengravers.com>, Alexander Sverdlin <alexander.sverdlin@gmail.com>, soc@kernel.org, Nikita Shubin <nikita.shubin@maquefel.me>, Arnd Bergmann <arnd@arndb.de>, Oleg Nesterov <oleg@redhat.com>, Hubert Feurstein <hubert.feurstein@contec.at>, Lukasz Majewski <lukma@denx.de>, Catalin Marinas <catalin.marinas@arm.com>, Will Deacon <will@kernel.org>, Nathan Chancellor <nathan@kernel.org>, Nick Desaulniers <ndesaulniers@google.com>, Linus Walleij <linus.walleij@linaro.org>, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, clang-built-linux@googlegroups.com Subject: Re: [PATCH] ARM: ep93xx: remove MaverickCrunch support Date: Mon, 2 Aug 2021 17:45:17 +0200 [thread overview] Message-ID: <CAL4-wQqCL1S-GYu7VKJeTT37wh=rR=SMUuwgKiXnnn_Y=uydOA@mail.gmail.com> (raw) In-Reply-To: <20210802141245.1146772-1-arnd@kernel.org> On 02/08/2021, Arnd Bergmann <arnd@kernel.org> wrote: > The MaverickCrunch support for ep93xx never made it into glibc This is true, but is not needed except for preserving FP registers in catch/throw exeptions or longjmps. > was removed from gcc in its 4.8 release in 2012. I was sad about that, as I had managed to get it working correctly in 4.2 4.3 and 4.4. Unfortunately the GCC ARM maintainer at the time was paid by ARM, and they had no interest in it, as I gather the ARM-Cirrus partnership ended up disappointingly. > It is now one of > the last parts of arch/arm/ that fails to build with the clang > integrated assembler Even if crunch support is not configured? > According to Hartley Sweeten: > > "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 It works fine on all production revisions except D0 (the first one) which is so rare as to be unfindable. All the others from D1 on have the exact same HW bugs. > there are still a number of hardware bugs that either give imprecise or garbage results. Not my experience, See http://martinwguy.net/crunch/#CorrectnessTests If "imprecise" means "doesn't handle unnormalized FP values correctly" then yes, that's a feature if you need the 2.5 to 4gimes speedup it provides. But I would be interested (Hartley) if you have a concrete example. > This touches mostly the ep93xx platform, The ep93xx is the only chip series it was ever included in. > If there are remaining users of MaverickCrunch, they can use LTS > kernels for at least another five years before kernel support ends. The only user ! am aware of is the HEAT deep space telescope in the Antarctic http://martinwguy.blogspot.com/2015/10/maverickcrunch-code-runs-on-heat-deep.html Personally I have no problem with removing kernel support if that makes people's lives easier in some way. M M
WARNING: multiple messages have this Message-ID (diff)
From: Martin Guy <martinwguy@gmail.com> To: Arnd Bergmann <arnd@kernel.org> Cc: Russell King <linux@armlinux.org.uk>, Hartley Sweeten <hsweeten@visionengravers.com>, Alexander Sverdlin <alexander.sverdlin@gmail.com>, soc@kernel.org, Nikita Shubin <nikita.shubin@maquefel.me>, Arnd Bergmann <arnd@arndb.de>, Oleg Nesterov <oleg@redhat.com>, Hubert Feurstein <hubert.feurstein@contec.at>, Lukasz Majewski <lukma@denx.de>, Catalin Marinas <catalin.marinas@arm.com>, Will Deacon <will@kernel.org>, Nathan Chancellor <nathan@kernel.org>, Nick Desaulniers <ndesaulniers@google.com>, Linus Walleij <linus.walleij@linaro.org>, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, clang-built-linux@googlegroups.com Subject: Re: [PATCH] ARM: ep93xx: remove MaverickCrunch support Date: Mon, 2 Aug 2021 17:45:17 +0200 [thread overview] Message-ID: <CAL4-wQqCL1S-GYu7VKJeTT37wh=rR=SMUuwgKiXnnn_Y=uydOA@mail.gmail.com> (raw) Message-ID: <20210802154517.SSmtmTFCZtbDR3xdS_Pj2qoCU1F5jtF9VXoHwLIT0c8@z> (raw) In-Reply-To: <20210802141245.1146772-1-arnd@kernel.org> On 02/08/2021, Arnd Bergmann <arnd@kernel.org> wrote: > The MaverickCrunch support for ep93xx never made it into glibc This is true, but is not needed except for preserving FP registers in catch/throw exeptions or longjmps. > was removed from gcc in its 4.8 release in 2012. I was sad about that, as I had managed to get it working correctly in 4.2 4.3 and 4.4. Unfortunately the GCC ARM maintainer at the time was paid by ARM, and they had no interest in it, as I gather the ARM-Cirrus partnership ended up disappointingly. > It is now one of > the last parts of arch/arm/ that fails to build with the clang > integrated assembler Even if crunch support is not configured? > According to Hartley Sweeten: > > "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 It works fine on all production revisions except D0 (the first one) which is so rare as to be unfindable. All the others from D1 on have the exact same HW bugs. > there are still a number of hardware bugs that either give imprecise or garbage results. Not my experience, See http://martinwguy.net/crunch/#CorrectnessTests If "imprecise" means "doesn't handle unnormalized FP values correctly" then yes, that's a feature if you need the 2.5 to 4gimes speedup it provides. But I would be interested (Hartley) if you have a concrete example. > This touches mostly the ep93xx platform, The ep93xx is the only chip series it was ever included in. > If there are remaining users of MaverickCrunch, they can use LTS > kernels for at least another five years before kernel support ends. The only user ! am aware of is the HEAT deep space telescope in the Antarctic http://martinwguy.blogspot.com/2015/10/maverickcrunch-code-runs-on-heat-deep.html Personally I have no problem with removing kernel support if that makes people's lives easier in some way. M M _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2021-08-02 15:45 UTC|newest] Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-08-02 14:11 [PATCH] ARM: ep93xx: remove MaverickCrunch support Arnd Bergmann 2021-08-02 15:45 ` Martin Guy [this message] 2021-08-02 15:45 ` Martin Guy 2021-08-02 15:45 ` Martin Guy 2021-08-03 11:40 ` Martin Guy 2021-08-03 11:40 ` Martin Guy 2021-08-03 11:40 ` Martin Guy 2021-08-03 11:58 ` Arnd Bergmann 2021-08-03 11:58 ` Arnd Bergmann 2021-08-03 15:52 ` Jerome Oufella 2021-08-03 15:52 ` Jerome Oufella 2021-08-03 15:52 ` Jerome Oufella 2021-08-03 17:11 ` Arnd Bergmann 2021-08-03 17:11 ` Arnd Bergmann 2021-08-03 12:12 ` Linus Walleij 2021-08-03 12:12 ` Linus Walleij 2021-08-03 12:12 ` Linus Walleij 2021-08-03 12:29 ` Arnd Bergmann 2021-08-03 12:29 ` Arnd Bergmann
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='CAL4-wQqCL1S-GYu7VKJeTT37wh=rR=SMUuwgKiXnnn_Y=uydOA@mail.gmail.com' \ --to=martinwguy@gmail.com \ --cc=alexander.sverdlin@gmail.com \ --cc=arnd@arndb.de \ --cc=arnd@kernel.org \ --cc=catalin.marinas@arm.com \ --cc=clang-built-linux@googlegroups.com \ --cc=hsweeten@visionengravers.com \ --cc=hubert.feurstein@contec.at \ --cc=linus.walleij@linaro.org \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linux@armlinux.org.uk \ --cc=lukma@denx.de \ --cc=nathan@kernel.org \ --cc=ndesaulniers@google.com \ --cc=nikita.shubin@maquefel.me \ --cc=oleg@redhat.com \ --cc=soc@kernel.org \ --cc=will@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: linkBe 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 NNTP newsgroup(s).