Re: [PATCH v4] arm64: support __int128 on gcc 5+

From: Jason A. Donenfeld
Date: Mon Nov 06 2017 - 19:01:42 EST

Next message: Ben Hutchings: "[PATCH 3.16 189/294] KEYS: don't let add_key() update an uninstantiated key"
Previous message: Ben Hutchings: "[PATCH 3.16 195/294] USB: fix out-of-bounds in usb_set_configuration"
In reply to: Jason A. Donenfeld: "[PATCH v5] arm64: support __int128 on gcc 5+"
Next in thread: Will Deacon: "Re: [PATCH v4] arm64: support __int128 on gcc 5+"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

On Tue, Nov 7, 2017 at 1:55 AM, Ard Biesheuvel
<ard.biesheuvel@xxxxxxxxxx> 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.

Next message: Ben Hutchings: "[PATCH 3.16 189/294] KEYS: don't let add_key() update an uninstantiated key"
Previous message: Ben Hutchings: "[PATCH 3.16 195/294] USB: fix out-of-bounds in usb_set_configuration"
In reply to: Jason A. Donenfeld: "[PATCH v5] arm64: support __int128 on gcc 5+"
Next in thread: Will Deacon: "Re: [PATCH v4] arm64: support __int128 on gcc 5+"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]