From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id 39E09138359 for ; Sat, 25 Jul 2020 08:03:08 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 68A68E081E; Sat, 25 Jul 2020 08:03:07 +0000 (UTC) Received: from mail-pj1-x1034.google.com (mail-pj1-x1034.google.com [IPv6:2607:f8b0:4864:20::1034]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 4803CE081E for ; Sat, 25 Jul 2020 08:03:07 +0000 (UTC) Received: by mail-pj1-x1034.google.com with SMTP id mn17so6575778pjb.4 for ; Sat, 25 Jul 2020 01:03:07 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=date:from:to:subject:message-id:references:mime-version :content-disposition:in-reply-to; bh=F45NDl0SSW6aw84aZoivkMHD8ZSLK7KiaX2oyllSuMQ=; b=EHUVv2ffmz728byMdmT2LvPfrbAWHZ3QDEjM9HjoCJalk3KxsOu/7EkVbzqMgO19lc +mJhOGUvJ+AjMOvPfjJUp/9Bke77XI4p+WaHMsSxRsd4ebPrFtXOnTjTsSbYS4Fi4tLQ VQItZ6g9TISSlFtIHvrenuEaUezDQ/yXm6kSlCOXSIY9i8CJiXP6mYV2I+3HFG/vAH2w S6Pwd5B/pRwoBN+S9iqsYwRWJU5HV21v0G4nwi5uSilocwWs+fLMrDIDqpmkGnLSazns Smz2qozgOiFyC3KB+kjCpsi17NUb8WYd6Lq31JElOyB1HCW2OzsFMM6Bzccw7M3kTTBm BFGw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:subject:message-id:references :mime-version:content-disposition:in-reply-to; bh=F45NDl0SSW6aw84aZoivkMHD8ZSLK7KiaX2oyllSuMQ=; b=QxDu4xYYTg0n/aayL+Urf2c9HjXg0Opb8vMoPeHE0WLNVLmJfpoFyTTw7Kqo8wtGnA tNQ12tgwY5Evyc61QMq6Ev3fCtGVhL2c34I8VTQ99UDiHyob0gVlqEtzyojPXAVubAHx 7miuU9pJaSKJbzt05CCKYQ+BAkgYSFYgwDimmS3ELkrhtggdgXZQPyFtdQEtS30f5PUA 7r5q7pBtLSGRPf+4ZjJDoQhkWi0JHpyHMP+FiQ2EFF1yTxIEC8BgooHXuHp3SgUFBGrF 7RwV4dEceh5a9rZLLg9VXXKq0CB/uMBYLlwinfX1UE7FO/aS3d6VaqGKLyqVgdtgVT6J BNCw== X-Gm-Message-State: AOAM5313n4okIOE7jIgr/7LQmL4nzCnFmu5+JSJFns0i1ahZwMqS1RqB ZA4hn2hxL8w74mJccQx8neYXZDPZ X-Google-Smtp-Source: ABdhPJzOoBrfCAmiWTuVdCnXPrRIxz3SoZGsgDRvTIZCzoHa2j5+YpCivR+GWRgRkLHMXxcUMZkWLQ== X-Received: by 2002:a17:902:904c:: with SMTP id w12mr11910822plz.147.1595664185963; Sat, 25 Jul 2020 01:03:05 -0700 (PDT) Received: from localhost ([106.215.5.42]) by smtp.gmail.com with ESMTPSA id u26sm8641004pfn.54.2020.07.25.01.03.04 for (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Sat, 25 Jul 2020 01:03:05 -0700 (PDT) Date: Sat, 25 Jul 2020 13:32:59 +0530 From: Gunwant Jain To: gentoo-soc@lists.gentoo.org Subject: Re: [gentoo-soc] Weekly Report: Portage Powered Android Message-ID: <20200725080259.yhh53qgehv7743zj@tardis.localdomain> References: <20200720074024.ayyqx5dk5hrngn7m@tardis.localdomain> <877dutngy8.fsf@robot.e.airelinux.org> <20200724150257.sngrh6wxazjxpggo@tardis.localdomain> <87v9icmh8e.fsf@robot.e.airelinux.org> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-soc@lists.gentoo.org Reply-to: gentoo-soc@lists.gentoo.org X-Auto-Response-Suppress: DR, RN, NRN, OOF, AutoReply MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="toy2nopet3d7fosn" Content-Disposition: inline In-Reply-To: <87v9icmh8e.fsf@robot.e.airelinux.org> X-Archives-Salt: dc89273d-ad1c-4904-9e6a-1f688e93698b X-Archives-Hash: a8165d4cb328cd841611a17629b448fa --toy2nopet3d7fosn Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 20/07/25 11:00AM, Benda Xu wrote: > Gunwant Jain writes: >=20 > > Yes it did. > > I can also report that llvm_android's stage1 clang is compiled for > > aarch64, I am on the stage2 step currently. >=20 > Good. Could you please remind me of the meanings of llvm stage1 and > stage2? Sure. AOSP provides its own distribution of LLVM. So most of what stage1 and stage2 I will be describing could be taken from [1].=20 Basically, we build LLVM stage1 using our own host toolchain. Then we use the newly built stage1 compiler to build stage2, the ready to use toolchain. Coming to how this goes in our use-case, if we were to build the LLVM toolchain using llvm_android (basically just build scripts), we will use a prebuilt Clang toolchain, bundled with llvm_android to build stage1.=20 Also AOSP targets only X86 architechture in stage1. After stage1 is built, the build script proceeds to start building stage2. This is where we use the newly built stage1 compilers to build stage2 compilers. AOSP targets AArch64, ARM, X86 and BPF when building stage2. Then the build script packages stage2 install and dumps the tar for our use. In the cycle of AOSP development, this newly packaged stage2 will be provided as the prebuilt LLVM toolchain in [2]. This repository is used: - In the AOSP tree, when someone builds a new custom ROM. - In llvm_android as the prebuilt toolchain used to build a version bumped stage1. For us, we will have to target AArch64 in building both stage1 and stage2. Regards, Gunwant [1] https://llvm.org/docs/BuildingADistribution.html [2] https://android.googlesource.com/platform/prebuilts/clang/host/linux-x8= 6/ --toy2nopet3d7fosn Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQEzBAABCAAdFiEEVcYcuddz0Grkn4q20gpuZPFudnkFAl8b5zMACgkQ0gpuZPFu dnlKNwf/aZrOBQb11y5HFq6uMC0BmI/Coof6eyMBfToY7elOBag3fW4UP3W8Gola tZ/zgI1XdOXLfyK9yl6OxxRs3cwjs/LhWh02l+9+09VZFrpsRosw0el/Ryfl9beP hKjlfsGDePF9h4FTGH1Gc4nZGb7tqmsKUoUz56g9WibLWJ6R1gvJ4zbI4JSD86NZ aUgbJn87CGCI0gyCe0aaPetmN91FfinaZGkieEqqHN/oa7v5r2b9OQKrn16oDcPn IZ+DnlglhNCQ83aYSUAWeQ4ParME2AcLYLY76zpJkLp9gZywZDJS6NhCJ9m6WV3I p9L+BAucDu7v6aMr/j6+0CKTUOUcaw== =MPQB -----END PGP SIGNATURE----- --toy2nopet3d7fosn--