From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from foss.arm.com (foss.arm.com [217.140.110.172]) by smtp.subspace.kernel.org (Postfix) with ESMTP id D0B4919AD85; Tue, 16 Jul 2024 13:49:51 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=217.140.110.172 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1721137793; cv=none; b=ktuddwUglplZbmmYnWA/S6ZcY4tXLpn6WDm7LQa3dp+1/aarmFt2915J4+MkoujVZCCzNoxuCNrdg6Nsv/HYGB0/bJsDQteMojtHlv3J9MbFmKhuFP15AQA/gWhIOpwAYJ/l+WD/Oe4kvtykhjYtw/myGwfokaLk40OvpyQWYIg= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1721137793; c=relaxed/simple; bh=hjq+HrXaifh2bOJJKxUdxktVT46Dj0YJp3PF85VTb/g=; h=Message-ID:Date:MIME-Version:Subject:To:Cc:References:From: In-Reply-To:Content-Type; b=t5kDgqbKMV8tW5PMV1hrXM9FVCQqpUE88W9BDqXtuKDuByK05AP43o04VfBQdgATncONLNntpSlP6b5Y8sShjlPxqLYQhb+qUwpYKp1GNcmz28VqqfZGFgXJeG1HlcGSkjY7chMC1ktuexPKy3IcM6EDih6Dfa2e+OzC8hRqiNE= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=arm.com; spf=pass smtp.mailfrom=arm.com; arc=none smtp.client-ip=217.140.110.172 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=arm.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=arm.com Received: from usa-sjc-imap-foss1.foss.arm.com (unknown [10.121.207.14]) by usa-sjc-mx-foss1.foss.arm.com (Postfix) with ESMTP id 5A1611063; Tue, 16 Jul 2024 06:50:16 -0700 (PDT) Received: from [10.2.76.71] (e132581.arm.com [10.2.76.71]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPSA id 72AC73F762; Tue, 16 Jul 2024 06:49:49 -0700 (PDT) Message-ID: <0c20b4b7-c1f6-4c0e-9f89-a99c25555640@arm.com> Date: Tue, 16 Jul 2024 14:49:47 +0100 Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: [PATCH v2] perf docs: Mark the Android document as obsolete To: Ian Rogers , clang-built-linux Cc: Arnaldo Carvalho de Melo , Namhyung Kim , Jiri Olsa , Adrian Hunter , "Liang, Kan" , Nathan Chancellor , Nick Desaulniers , Bill Wendling , Justin Stitt , James Clark , linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org References: <20240715143342.52236-1-leo.yan@arm.com> <1487da55-24dc-40ef-a6e8-4bf4b153fdc3@arm.com> Content-Language: en-US From: Leo Yan In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit On 7/16/24 14:30, Ian Rogers wrote: > On Tue, Jul 16, 2024 at 3:06 AM Leo Yan wrote: [...] >> Thanks for correcting. Now I even can build successfully with the Clang >> from Android NDK with an additional flag 'NO_DEMANGLE=1'. Though we still >> need to disable several modules for passing the building, but we are on the >> right way. >> >> Would you like to continue a formal fixing or you want me to follow up? > > +clang-built-linux > > If you could follow up it would be great! Okay, I will look into it. > I'm not sure how we detect > in the build that we're using clang, I suspect there is an approach in > a different kernel Makefile/Build that already tackles this but my > quick searching didn't yield anything - perhaps the change would be > better suited to the location the CROSS_COMPILE prefix is added to > gcc. Should we follow up the steps in the Documentation/kbuild/llvm.rst? The document uses the flag 'LLVM=1' for selecting LLVM/Clang. Thanks, Leo > The only thing the change to Makefile.config is doing is > injecting the --target option. I'm not sure anything more is not > working for me on my laptop with this approach compared to cross > compiling with gcc, but as you say going in the right direction is > worth it anyway. > > Thanks, > Ian