Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
MIME-Version: 1.0
References: <20200914133626.hlsvu5kces3wsirr@google.com> <20210125200756.1249239-1-oupton@google.com>
 <87pn1ska6c.wl-maz@kernel.org>
In-Reply-To: <87pn1ska6c.wl-maz@kernel.org>
From:   Oliver Upton <oupton@google.com>
Date:   Tue, 26 Jan 2021 10:23:25 -0800
Message-ID: <CAOQ_QshK6HoaLqbaCVEgOPACK==Wb3-ADUhoUeQ0W67bK9zqqw@mail.gmail.com>
Subject: Re: [BUG]: KVM: arm64: Fix symbol dependency in __hyp_call_panic_nvhe
To:     Marc Zyngier <maz@kernel.org>
Cc:     Sasha Levin <sashal@kernel.org>, dbrazdil@google.com,
        hns@goldelico.com,
        Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Content-Type: text/plain; charset="UTF-8"
Precedence: bulk

On Mon, Jan 25, 2021 at 12:56 PM Marc Zyngier <maz@kernel.org> 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"), which forbids GCC 4.9 as it has been
>   demonstrated to mis-compile the kernel (and this patch is targeting
>   stable anyway)

If the latter is hitting stable then it sounds like high time to throw
out my broken GCC. Thanks Marc!

--
Oliver