From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
        id S933090AbdKGABk (ORCPT <rfc822;w@1wt.eu>);
        Mon, 6 Nov 2017 19:01:40 -0500
Received: from frisell.zx2c4.com ([192.95.5.64]:39657 "EHLO frisell.zx2c4.com"
        rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
        id S932831AbdKGABh (ORCPT <rfc822;linux-kernel@vger.kernel.org>);
        Mon, 6 Nov 2017 19:01:37 -0500
X-Google-Smtp-Source: ABhQp+SCuxvOun1PYGkXlbalqJxRxSg3DITHnCpkXVVFNm8+q1cAXpz56hHNJmAGprtjbddoYtAm6ytrsf4pOYauY5I=
MIME-Version: 1.0
In-Reply-To: <CAKv+Gu94w3f0n4qDeR3uC5nVaKwjTUYf8W4cs5L3nE1HxoDG9Q@mail.gmail.com>
References: <20171103141858.13149-1-Jason@zx2c4.com> <20171106093151.8312-1-Jason@zx2c4.com>
 <20171106155917.glgjgipppzsdpp6h@armageddon.cambridge.arm.com>
 <20171106161459.bm4b2c7ahljluuda@armageddon.cambridge.arm.com>
 <CAHmME9p+ef-+fmdiO15LU7X3Sr-CDyngpPwKZN2FqOQmZNjLtg@mail.gmail.com> <CAKv+Gu94w3f0n4qDeR3uC5nVaKwjTUYf8W4cs5L3nE1HxoDG9Q@mail.gmail.com>
From: "Jason A. Donenfeld" <Jason@zx2c4.com>
Date: Tue, 7 Nov 2017 09:01:34 +0900
X-Gmail-Original-Message-ID: <CAHmME9o7_g=_yofAMBaABrPzbVrKryv9ucb=MhAB6CGC6g=4tA@mail.gmail.com>
Message-ID: <CAHmME9o7_g=_yofAMBaABrPzbVrKryv9ucb=MhAB6CGC6g=4tA@mail.gmail.com>
Subject: Re: [PATCH v4] arm64: support __int128 on gcc 5+
To: Ard Biesheuvel <ard.biesheuvel@linaro.org>
Cc: Catalin Marinas <catalin.marinas@arm.com>,
        Mark Rutland <mark.rutland@arm.com>,
        Kefeng Wang <wangkefeng.wang@huawei.com>,
        Arnd Bergmann <arnd@arndb.de>, Will Deacon <will.deacon@arm.com>,
        LKML <linux-kernel@vger.kernel.org>,
        "linux-arm-kernel@lists.infradead.org" 
        <linux-arm-kernel@lists.infradead.org>
Content-Type: text/plain; charset="UTF-8"
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

On Tue, Nov 7, 2017 at 1:55 AM, Ard Biesheuvel
<ard.biesheuvel@linaro.org> wrote:
> It appears your v4 adds __ashlti3() and __ashrti3, whereas the error
> is about __lshrti3() being undefined.

Whoopsie. v5 adds the final missing function. Looks like it now
compiles for -next with the config you provided me.