From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751608AbdJaLRO (ORCPT ); Tue, 31 Oct 2017 07:17:14 -0400 Received: from frisell.zx2c4.com ([192.95.5.64]:59965 "EHLO frisell.zx2c4.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750872AbdJaLRN (ORCPT ); Tue, 31 Oct 2017 07:17:13 -0400 X-Google-Smtp-Source: ABhQp+R53hKsziUpYohCDcMxiTcYCRKfiueH6gyG0VV6I8d+rYVLHdCxmfzJQ2JJxW0P/N/3Upm4Q9RErpGhxUcfYT0= MIME-Version: 1.0 In-Reply-To: <20171031104332.gqpd6icvrxt2uj4c@lakrids.cambridge.arm.com> References: <20171031104332.gqpd6icvrxt2uj4c@lakrids.cambridge.arm.com> From: "Jason A. Donenfeld" Date: Tue, 31 Oct 2017 12:17:10 +0100 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: CONFIG_ARCH_SUPPORTS_INT128 for AArch64 To: Mark Rutland Cc: linux-arm-kernel@lists.infradead.org, LKML Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Mark, On Tue, Oct 31, 2017 at 11:43 AM, Mark Rutland wrote: > Judging by Documentation/kbuild/makefiles.txt, we could do something > like the below in the arm64 Makefile: > > cflags-y += $(call cc-ifversion, -ge, 0500, -DCONFIG_ARCH_SUPPORTS_INT128) Okay, in that case, I'll re-research the gcc commit that made int128 work properly on aarch64, confirm the release version, and then submit a patch doing this. Jason