On Mon, Jan 25, 2021 at 12:56 PM Marc Zyngier wrote:
> - Cherry-pick 9fd339a45be5 ("arm64: Work around broken GCC 4.9
> handling of "S" constraint"), which works around this particular GCC
> bug
>
> - Cherry-pick dca5244d2f5b ("compiler.h: Raise minimum version of GCC
> to 5.1 for arm64"),
Hi all,
On Mon, 25 Jan 2021 20:07:56 +,
Oliver Upton wrote:
>
> > That means we have two options:
> > (a) define __hyp_panic_string in a different .c file in all pre-5.9
> > branches, or
> > (b) revert the backported patch.
> >
> > The patch was needed in 5.9 and should stay there. It
> That means we have two options:
> (a) define __hyp_panic_string in a different .c file in all pre-5.9 branches,
> or
> (b) revert the backported patch.
>
> The patch was needed in 5.9 and should stay there. It wasn't needed in earlier
> versions because the symbol was being kept alive by
Hi Nikolaus,
> > Right, it got moved around in upstream.
>
> Maybe this has fixed something...
>
Thanks for reporting this. I've managed to reproduce the problem with Linaro
GCC 4.9.4 and I can also confirm that the same toolchain builds v5.9-rc5 fine.
As Sasha pointed out, the patch was part
Hi,
it seems as if your patch
34f379956e9d7 ("KVM: arm64: Fix symbol dependency in __hyp_call_panic_nvhe")
[ Upstream commit b38b298aa4397e2dc74a89b4dd3eac9e59b64c96 ]
fails to compile in v5.8.7 for me (using an aarch64 gcc 4.9 cross-toolchain to
try
to build a kernel for the PinePhone):
CC
Hi,
> Am 07.09.2020 um 16:22 schrieb Sasha Levin :
>
> On Mon, Sep 07, 2020 at 03:29:40PM +0200, H. Nikolaus Schaller wrote:
>> Hi,
>> it seems as if your patch
>>
>> 34f379956e9d7 ("KVM: arm64: Fix symbol dependency in __hyp_call_panic_nvhe")
>> [ Upstream commit
On Mon, Sep 07, 2020 at 03:29:40PM +0200, H. Nikolaus Schaller wrote:
Hi,
it seems as if your patch
34f379956e9d7 ("KVM: arm64: Fix symbol dependency in __hyp_call_panic_nvhe")
[ Upstream commit b38b298aa4397e2dc74a89b4dd3eac9e59b64c96 ]
fails to compile in v5.8.7 for me (using an aarch64 gcc
7 matches
Mail list logo
