acpl(1)

💅 acpl — a whole manual page, bestie

okay so welcome to acpl(1), straight out of the Scotch user's manual. yes, the Scotch. no, not the drink (sadly). it's giving compiler energy and honestly? iconic. 🎀

---

✨ NAME ✨

acpl — compile a target architectures 🦋

(yes the original really does say "a target architectures". we respect the grammar choices of the elders. periodt.)

---

🌸 SYNOPSIS 🌸

acpl [options] [itfile] [otfile]

---

👑 DESCRIPTION 👑

so here's the tea, bestie: acpl takes a decomposition-defined target architecture file — that's itfile, and its type is 'deco 0' — and compiles it into a compiled decomposition-defined target architecture of type 'deco 1', which gets stored in otfile. glow up from 'deco 0' to 'deco 1', fr fr. ✨

and what does "compiling" even mean here? it means computing the distance matrix of all possible subdomains, using the distance matrix of all terminal subdomains that was handed to you in the 'deco 0' format. that's the whole vibe. 🧚

💀 now the part you actually need to hear: this computation happens internally every single time a 'deco 0' format gets read, and it's quadratic in time. so if you're out here repeatedly computing mappings on a large decomposition-defined 'deco 0' target architecture, you are lowkey wasting time over and over. pre-compiling it with acpl once? that's the main character move. it saves you time. 🫶

compressed files, bestie!! when the proper libraries were included at compile time, acpl can directly handle compressed files — both as input and output. a stream gets treated as compressed whenever its name is postfixed with a compressed file extension, like in 'brol.tgt.bz2' or '-.gz'. the compression formats that can be supported are:

• the bzip2 format — '.bz2'
• the gzip format — '.gz'
• the lzma format — '.lzma'

and WHY should you care about compression? because decomposition-defined target architecture files have a size that is quadratic in the number of target vertices — blame the distance matrix structures, they're dramatic 💅 — so storing them compressed may save you a lot of space. especially for compiled target architecture files. so much space. obsessed. 🍓

---

💜 OPTIONS 💜

• -h — display some help. that's it. that's the flag. 🎀
• -V — display program version and copyright. serve the receipts, king. 👑

---

🌈 EXAMPLE 🌈

okay so imagine you wanna create a compiled cube-connected-cycle target architecture of dimension 4, and save it under the gzip(1) format to file 'ccc4c.tgt.gz'. 🌸

the dash '-' standard file name is doing the lord's work here: it means the 'deco 0' target architecture description produced by amk_ccc(1) gets read from the standard input, through the pipe. piping? we love to see it. 🧚

$ amk_ccc 4 | acpl - ccc4c.tgt.gz

look at that. one line. iconic. no cap. ✨

---

🔥 SEE ALSO 🔥

amk_grf(1), amk_ccc(1), atst(1), dgmap(1), gmap(1), gmtst(1).

Scotch user's manual.

---

🦋 AUTHOR 🦋

Francois Pellegrini <francois.pellegrini@labri.fr>

---

and that's the whole page bestie, you absolutely ate 💅✨

drop your thanks to the Scotch user's manual, version vibes from 16 June 2026, filed under acpl(1) — mwah, go compile something gorgeous. 🎀💖