[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAHmME9oXG1AgkJM-Ya6Jns+Y6HadwGxQ+NqmF0ed=p8Zg8fiVg@mail.gmail.com>
Date: Fri, 3 Nov 2017 15:14:13 +0100
From: "Jason A. Donenfeld" <Jason@...c4.com>
To: Will Deacon <will.deacon@....com>
Cc: linux-arm-kernel@...ts.infradead.org,
LKML <linux-kernel@...r.kernel.org>,
Mark Rutland <mark.rutland@....com>,
wangkefeng.wang@...wei.com,
Ard Biesheuvel <ard.biesheuvel@...aro.org>
Subject: Re: [PATCH v2] arm64: support __int128 on gcc 5+
On Fri, Nov 3, 2017 at 2:42 PM, Will Deacon <will.deacon@....com> wrote:
> We used to link against libgcc way back when, but that dependency was
> removed in commit d67703a8a69e ("arm64: kill off the libgcc dependency")
> and I'm really not keen to add it back. I also think that there might
> be licensing concerns if you link against it and make use of GCC plugins,
> but IANAL.
Considering many other architectures link to it, that seems strange to me...
>
> Shouldn't we just provide our own implementations of __ashlti3 and
> __ashrti3 instead?
I just coded up an implementation. I'm testing it now and I'll have v3
for you shortly.
Jason
Powered by blists - more mailing lists