Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751239AbdHRGzm (ORCPT ); Fri, 18 Aug 2017 02:55:42 -0400 Received: from mail-qt0-f179.google.com ([209.85.216.179]:34924 "EHLO mail-qt0-f179.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751007AbdHRGzk (ORCPT ); Fri, 18 Aug 2017 02:55:40 -0400 MIME-Version: 1.0 In-Reply-To: <20170808.203540.2238751604302920304.davem@davemloft.net> References: <20170807130602.31785-4-joelaf@google.com> <20170807.112840.395506747161262549.davem@davemloft.net> <20170808.203540.2238751604302920304.davem@davemloft.net> From: Joel Fernandes Date: Thu, 17 Aug 2017 23:55:38 -0700 Message-ID: Subject: Re: [PATCH RFC v2 3/5] samples/bpf: Fix inline asm issues building samples on arm64 To: David Miller Cc: LKML , Chenbo Feng , Alison Chaiken , Juri Lelli , Alexei Starovoitov , Daniel Borkmann , "open list:BPF (Safe dynamic programs and tools)" Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1187 Lines: 30 On Tue, Aug 8, 2017 at 8:35 PM, David Miller wrote: > From: Joel Fernandes > Date: Mon, 7 Aug 2017 18:20:49 -0700 > >> On Mon, Aug 7, 2017 at 11:28 AM, David Miller wrote: >>> The amount of hellish hacks we are adding to deal with this is getting >>> way out of control. >> >> I agree with you that hellish hacks are being added which is why it >> keeps breaking. I think one of the things my series does is to add >> back inclusion of asm headers that were previously removed (that is >> the worst hellish hack in my opinion that existing in mainline). So in >> that respect my patch is an improvement and makes it possible to build >> for arm64 platforms (which is currently broken in mainline). > > Yeah that is a problem. > > Perhaps another avenue of attack is to separate "type" header files from > stuff that has functiond declarations and inline assembler code. I was thinking that's probably a huge undertaking if you meant doing the above for every arch? Also another way could be to modify clang to ignore inline asm directives during compilation? Do you have any comments about such approach? thanks, -Joel