public inbox for gentoo-soc@lists.gentoo.org
 help / color / mirror / Atom feed
From: Gunwant Jain <therealgunwant@gmail.com>
To: gentoo-soc@lists.gentoo.org
Subject: Re: [gentoo-soc] Weekly Report: Portage Powered Android
Date: Sat, 25 Jul 2020 13:51:12 +0530	[thread overview]
Message-ID: <20200725082112.b3s4yoz5hxkff676@tardis.localdomain> (raw)
In-Reply-To: <20200725080259.yhh53qgehv7743zj@tardis.localdomain>

[-- Attachment #1: Type: text/plain, Size: 2328 bytes --]

I am sorry to add on like this, but if it was not mentioned, I am not
using any prebuilt repository AOSP bundled with llvm_android. This is
the reason why I spent the time emerging Clang on my phone; for using it
to build stage1.
Although if advised otherwise, I could potentially break the AOSP
development cycle for our use and start the same cycle but with prebuilt
LLVM toolchain for AArch64 host instead of X86. I could expand on how to
do this, if you would like.

On 20/07/25 01:33PM, Gunwant Jain wrote:
> On 20/07/25 11:00AM, Benda Xu wrote:
> > Gunwant Jain <therealgunwant@gmail.com> writes:
> > 
> > > Yes it did.
> > > I can also report that llvm_android's stage1 clang is compiled for
> > > aarch64, I am on the stage2 step currently.
> > 
> > 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]. 
> 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. 
> 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-x86/



[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  reply	other threads:[~2020-07-25  8:21 UTC|newest]

Thread overview: 49+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-20  7:40 [gentoo-soc] Weekly Report: Portage Powered Android Gunwant Jain
2020-07-24 14:08 ` Benda Xu
2020-07-24 15:02   ` Gunwant Jain
2020-07-24 17:07     ` UnderSampled
2020-07-24 18:12       ` Gunwant Jain
2020-07-25  3:00     ` Benda Xu
2020-07-25  8:02       ` Gunwant Jain
2020-07-25  8:21         ` Gunwant Jain [this message]
  -- strict thread matches above, loose matches on Subject: below --
2020-08-17 18:05 Gunwant Jain
2020-08-17 23:15 ` Benda Xu
2020-08-20  6:21   ` Gunwant Jain
2020-08-12  1:41 Gunwant Jain
2020-08-12  7:34 ` EBo
2020-08-14  7:26   ` Gunwant Jain
2020-07-30 15:00 Gunwant Jain
2020-07-13 23:09 Gunwant Jain
2020-07-14  0:17 ` Benda Xu
2020-07-14  5:01   ` Gunwant Jain
2020-07-15  1:04     ` Benda Xu
2020-07-15  1:09       ` UnderSampled
2020-07-15  4:55         ` Gunwant Jain
2020-07-15  4:45       ` Pengcheng Xu
2020-07-15  4:58         ` Gunwant Jain
2020-07-15  4:52       ` Gunwant Jain
2020-07-14  4:05 ` Pengcheng Xu
2020-07-14  5:05   ` Gunwant Jain
2020-07-08 11:39 Gunwant Jain
2020-07-08 13:53 ` Pengcheng Xu
2020-07-09  1:04 ` Benda Xu
2020-06-29 20:12 Gunwant Jain
2020-06-29 21:27 ` EBo
2020-06-30 21:42   ` Gunwant Jain
2020-07-01  2:37     ` EBo
2020-07-01  3:15       ` Gunwant Jain
2020-07-01 12:40     ` Lucas Ramage
2020-07-01  7:17 ` Benda Xu
2020-07-01 16:12   ` Gunwant Jain
2020-07-01 14:07 ` Pengcheng Xu
2020-07-01 16:53   ` Gunwant Jain
2020-07-02  3:50     ` UnderSampled
2020-07-02 12:14       ` Gunwant Jain
2020-06-22 19:15 Gunwant Jain
2020-06-23  4:45 ` Pengcheng Xu
2020-06-23 11:44   ` Gunwant Jain
2020-07-01  7:14 ` Benda Xu
2020-06-15  8:03 Gunwant Jain
2020-07-01  7:10 ` Benda Xu
2020-06-09 11:39 Gunwant Jain
2020-07-01  7:08 ` Benda Xu

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20200725082112.b3s4yoz5hxkff676@tardis.localdomain \
    --to=therealgunwant@gmail.com \
    --cc=gentoo-soc@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox