Pimp My IDE / garage dispatch
Back to garage
September 30, 2026 | compiler front ends / open source / integration

Public source is the first custody stamp.

EDG's C and C++ front end is now public. That opens the hood. It does not tell your toolchain when to trust the engine.

Treat the move as a custody transfer. Check the source, reproduce the build, test your language cases, and replay the product integration.

A mature engine just changed hands.

On September 30, Edison Design Group published the source for its C and C++ front end. The C++ Alliance is now its nonprofit home. EDG says John Spicer remains the point of contact and chairs the fiscal sponsorship committee.[1]

The public repository is substantial. Its README describes a configurable front end, C and C++ source-generating back ends, a prelinker, runtime support, intermediate-language utilities, a demangler, and development tools. The repository also exposes its history, issue tracker, contribution guide, tests, and documentation.[2]

Opening the hood changes access. It does not finish adoption.

The license opens a real route.

The repository's license text is Apache License 2.0 with LLVM exceptions. The exception covers code embedded in object output by compilation. The file also warns that separately identified third-party code can carry different terms.[3]

That is enough to make evaluation practical. It is not a substitute for checking the exact revision, bundled code, notices, and distribution plan that your product will use.

The build is configurable by design.

EDG documents a direct route based on a generated src/defines.h and a C++14 compiler. Its supported project build uses Python, CMake, a C or C++ compiler, and usually Ninja. Presets cover macOS, Linux, and Windows debug and release builds.[4]

That configurability is useful because compiler front ends rarely enter products as untouched executables. It also means a green upstream build says little about your dialect flags, bug-compatibility settings, diagnostics, intermediate-language consumers, or source transformation path.

Make the handoff produce four records.

First, pin the source revision and license inventory. Second, save the toolchain, configuration, and build output. Third, run the language cases that matter to your users. Fourth, replay the integration that consumes diagnostics, generated code, or intermediate-language data.

This page inspected the public repository and its documentation. It did not compile the front end or run conformance tests. The control below creates a review template. It does not turn repository access into product evidence.

Interactive makeover / compiler custody rack

Move the crate through inspection

Traditional purpose replaced: a static migration checklist. Better version: one custody stage drives the physical route, review prompt, status, and copyable handoff card.

Choose the active stage

The stage selector changes the question under review. The checkboxes only choose sections for the handoff template.

Custody station
Handoff template sections
Handoff card draft0 of 4 sections selected
Illustrative custody route

Compiler custody rack

Can you identify the exact code?

Record the commit, license files, notices, and any third-party directories before evaluating a build.

Selecting every section means the template structure is ready. It does not prove the compiler built, passed a case set, or worked inside a product.

Adoption order / four records

Keep each proof attached to its claim.

01 / SOURCE

Pin custody

Save the revision, license inventory, notices, and upstream location.

02 / BUILD

Reproduce one artifact

Record the toolchain, preset, configuration, output hash, and failures.

03 / CASES

Test your dialect

Run the extensions, diagnostics, compatibility cases, and regressions you need.

04 / INTEGRATION

Replay the consumer

Test the product path that reads diagnostics, generated code, or intermediate data.

Sources read

Source log and evidence boundary
  1. EDGCPP, "Open Source Transition", read September 30, 2026. This first-party page announces the public source, C++ Alliance stewardship, committee structure, funding tracks, and continuity plan.
  2. EDG compiler repository, inspected September 30, 2026. The public repository and README document the front end, back ends, prelinker, intermediate-language tools, tests, contribution files, and development history.
  3. EDG compiler license file, read September 30, 2026. It contains Apache License 2.0 with LLVM exceptions and the repository's third-party-code notice.
  4. EDG compiler build instructions, read September 30, 2026. It documents requirements, direct compilation, CMake presets, supported toolchains, and the Ninja build route.
  5. Hacker News discussion, exact item 49913192, checked September 30, 2026. It led to the announcement. It is not evidence for compiler behavior.

Evidence boundary: this dispatch verifies that the repository, license text, and build instructions are public. It does not claim that the front end was built here, that it passes a conformance suite, or that it fits a specific product integration.