18
Self-host your compiler, you cowards! (blog.goodanser.com)
submitted 4 months ago by to c/programming@programming.dev
8 comments fedilink hide all child comments
 

Self-host your compiler, you cowards! Several times this year, I've read about new systems programming languages, usually created with robotic help. That's great! New languages expand how we think about programming. I've noticed their compilers are almost always written in Rust. Rust is a fine systems programming language in its own right, but a systems programming language, the kind of language meant for writing things like compilers, ought to be used for its own compiler before it's used for any other serious work. I'm kidding about the cowards part of course. I'm sure all language designers are brave and kind, even if some look like serial killers. @programming@programming@programming.dev #programming #languagedesign #rust #compilers

you are viewing a single comment's thread
view the rest of the comments
[–] 2 points 4 months ago (2 children)

There's a breakdown in the link in my previous comment:

Why does AOSP build consume so much memory

From my experience, building a custom ROM based on AOSP indeed requires about 30-40GB of memory. It may be more for ROMs with more requirements, such as LineageOS-based ROMs.

Just lower the number of jobs!

Well, this doesn’t work. Why? The Android build process occurs in multiple stages:

  • Build dependency analysis: The build system (Soong) analyzes de build dependencies by parsing the .bp blueprint files. A dependency graph is generated to determine the build order, with relationships between thousands of modules. As far as I know, the number of jobs doesn’t matter: everything is loaded in memory, and that uses about 30 GB of memory or more with Android 14 (this includes RAM and swap). This step uses a huge fixed amount of memory, regardless of the number of jobs.

  • Compilation and Linking: these steps can be run in parallel, so the number of jobs will determine how much memory will be needed. From my experience, with 8 jobs, less than 30 GB are used.

  • Image generation: It is quite RAM-hungry, but I remember it consumes less than 10 GB on my build setup.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 2 points 4 months ago (1 child)

    Ok, but how is a dependency tree 30 GB heavy?

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •
  • [–] 4 points 4 months ago* (last edited 4 months ago)

    Apparently there are thousands of code modules and Soong keeps literally everything in memory while calculating dependencies? Which makes me wonder what the hell the blueprint files actually do if it's still so absurdly heavy.

    Considering how the requirements went from four gigs to over thirty over the years, it wouldn't shock me if RAM use grows exponentially with the number of modules and they just put up with it because the Google devs use cloud machines with practically infinite resources for building and therefore don't have any impetus to fix it.

  • permalink
  • fedilink
  • source
  • parent