Can (deprecated) Native Client concept and .nexe file be useful here?

[guest271314]

TL;DR (WebAssembly/wabt#1864; GoogleChrome/developer.chrome.com#2295; https://stackoverflow.com/q/70694704) I unsuccessfully tried to reverse-engineer tts_service_x86_64.nexe, a Google speech synthesis engine executable used for US English Female Text-to-speech (by Google).

The strings the executable of tts_service_x86_63.nexe https://gist.github.com/guest271314/4894662d31ffb4ad2cd57683721bf4b4.

NaCl and PNaCl

Portable Native Client (PNaCl)
PNaCl solves the portability problem by splitting the compilation process into two parts:

• compiling the source code to a bitcode executable (pexe), and
• translating the bitcode to a host-specific executable as soon as the module loads in the browser but before any code execution.
  ...
  With PNaCl, you’ll generate a single pexe, rather than multiple platform- specific nexes...

From Aligned bundling support in LLVM at Implementation in LLVM MC

The following description will focus on the path: Text assembly -> ELF object streamer -> Assembly -> Object file emission. This path can be roughly divided to three stages:

1. Parse bundling directives and emit a sequence of sections (MCSectionData) and fragments (MCFragment derivatives) that represent the input.
2. Perform layout of the fragments to be valid w.r.t. relaxation and bundling.
3. Write the output object.

[RaisinTen]

I didn't dig too deep but is this about creating a single binary that would run on all platforms?