[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Yn1DT3zHNM9MMQJL@osiris>
Date: Thu, 12 May 2022 19:26:39 +0200
From: Heiko Carstens <hca@...ux.ibm.com>
To: Nick Desaulniers <ndesaulniers@...gle.com>
Cc: Jonas Paulsson <paulsson@...ux.vnet.ibm.com>,
Vasily Gorbik <gor@...ux.ibm.com>,
Alexander Gordeev <agordeev@...ux.ibm.com>,
Ulrich Weigand <ulrich.weigand@...ibm.com>,
Masahiro Yamada <masahiroy@...nel.org>,
Alexander Egorenkov <egorenar@...ux.ibm.com>,
Sven Schnelle <svens@...ux.ibm.com>,
Andreas Krebbel <krebbel@...ux.ibm.com>,
Nathan Chancellor <natechancellor@...il.com>,
linux-kernel@...r.kernel.org, linux-s390@...r.kernel.org
Subject: Re: [PATCH 5/8] s390/purgatory: workaround llvm's IAS limitations
On Wed, May 11, 2022 at 12:54:41PM -0700, Nick Desaulniers wrote:
> On Wed, May 11, 2022 at 5:05 AM Heiko Carstens <hca@...ux.ibm.com> wrote:
> >
> > llvm's integrated assembler cannot handle immediate values which are
> > calculated with two local labels:
> >
> > arch/s390/purgatory/head.S:139:11: error: invalid operand for instruction
> > aghi %r8,-(.base_crash-purgatory_start)
>
> I thought this was fixed in
> https://github.com/ClangBuiltLinux/linux/issues/1420
> https://reviews.llvm.org/D113341
> (clang-14)
> ?
Looks like the referenced fix only works for displacements, bit not
for immediates.
Powered by blists - more mailing lists