From: Russell King - ARM Linux admin <linux@armlinux.org.uk>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Nick Desaulniers <ndesaulniers@google.com>,
Linus Walleij <linus.walleij@linaro.org>,
Linux ARM <linux-arm-kernel@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
clang-built-linux <clang-built-linux@googlegroups.com>
Subject: Re: [PATCH] ARM: mtd-xip: work around clang/llvm bug
Date: Tue, 9 Jul 2019 23:25:17 +0100 [thread overview]
Message-ID: <20190709222517.c3nn6fgrz2eost3s@shell.armlinux.org.uk> (raw)
In-Reply-To: <CAK8P3a2anB0hD5J0JfPpJ_Gjc=NjoNC4k9nJ=t9H5AOBbdnfqg@mail.gmail.com>
On Tue, Jul 09, 2019 at 08:40:51PM +0200, Arnd Bergmann wrote:
> On Tue, Jul 9, 2019 at 8:08 PM 'Nick Desaulniers' via Clang Built
> Linux <clang-built-linux@googlegroups.com> wrote:
> > On Tue, Jul 9, 2019 at 1:41 AM Linus Walleij <linus.walleij@linaro.org> wrote:
> >
> > > I guess this brings up the old question whether the compiler should
> > > be worked around or just considered immature, but as it happens this
> >
> > Definitely a balancing act; we prioritize work based on what's
> > feasible to work around vs must be implemented. A lot of my time is
> > going into validation of asm goto right now, but others are ramping up
> > on the integrated assembler (clang itself can be invoked as a
> > substitute for GNU AS; but there's not enough support to do `make
> > AS=clang` for the kernel just yet).
>
> Note that this bug is the same with both gas and AS=clang, which also
> indicates that clang implemented the undocumented .rep directive
> for compatibility.
>
> Overall I think we are at the point where building the kernel with clang-8
> is mature enough that we should work around bugs like this where it is
> easy enough rather than waiting for clang-9.
While both assemblers seem to support both .rept and .rep, might it
be an idea to check what the clang-8 situation is with .rept ?
--
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTC broadband for 0.8mile line in suburbia: sync at 12.1Mbps down 622kbps up
According to speedtest.net: 11.9Mbps down 500kbps up
next prev parent reply other threads:[~2019-07-09 22:25 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-08 20:30 [PATCH] ARM: mtd-xip: work around clang/llvm bug Arnd Bergmann
2019-07-08 20:54 ` Nick Desaulniers
2019-07-09 8:41 ` Linus Walleij
2019-07-09 9:17 ` Russell King - ARM Linux admin
2019-07-09 11:48 ` Linus Walleij
2019-07-09 18:07 ` Nick Desaulniers
2019-07-09 18:40 ` Arnd Bergmann
2019-07-09 22:25 ` Russell King - ARM Linux admin [this message]
2019-07-10 8:33 ` Arnd Bergmann
2019-07-10 8:58 ` Russell King - ARM Linux admin
2019-07-09 12:17 ` Linus Walleij
2019-07-09 12:25 ` Russell King - ARM Linux admin
2019-07-09 18:11 ` 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=20190709222517.c3nn6fgrz2eost3s@shell.armlinux.org.uk \
--to=linux@armlinux.org.uk \
--cc=arnd@arndb.de \
--cc=clang-built-linux@googlegroups.com \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ndesaulniers@google.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 NNTP newsgroup(s).