Somebody gave you a compiler
It is a real one: built for their code, measured on real hardware, and it runs on your machine offline once it is installed. Here is what it will and will not do for you, and the one thing you need before you can use it.
What you cannot do yet
Some of what this page describes is not available yet. None of it is a decision you need to make — saying so here is better than letting you find out one at a time.
- Nothing has been frozen into a compiler through the service yet. Receiving one, running it and working out which parts of it fit a different program are all built. What has not happened is the first one being made, so there is nothing for anybody to send you. What that page describes is what it is for rather than what anyone can do today.
Everything else on this page describes how it works today. Where something is not built yet it is in this list — if you find a claim that is not, that is a bug in this block and not a feature we are being coy about.
You will need an account to import it
Bringing somebody else's compiler onto your machine requires signing up. Saying so here rather than at the moment you try is deliberate — nobody should meet that halfway through.
After that it is yours to run: offline, on your own machine, with no lookup and nothing reporting back. The account is what compilers are made and kept against, not a meter on using one.
- 01 proposed 12 marks
- 02 proved 7 marks
- 03 faster 4 marks
- 04 admitted 2 marks
- 05 one compiler one
What it will do for your code
Some of what it does will apply to your program and some will not. A compiler is tuned to one program on one kind of machine — that is where the advantage comes from, and it is exactly why it does not transfer whole. Their compiler carries the transformations that were worth it for their code, with parameters measured on their hardware.
The step that takes a compiler somebody else made and works out which parts of it fit your code is built and passes end to end. What has not happened yet is anybody freezing a compiler through the service, so if you are reading this holding one, it did not come from here.
It is never worse than your default compiler: where nothing it knows applies, you get your ordinary build. That is enforced at the moment you compile — any failure on the tuned path yields a byte-identical ordinary build, and 37 tests hold it there. The same check made when a compiler is released rather than when it runs is the half that is not written yet, so treat the release-time guarantee as the intended floor rather than one anything currently keeps.
How much of that survives the trip to your program is a real question with a real answer, and nobody can tell you what it is without measuring. Not us, and not the person who sent it to you.
If you want it tuned for your code
You point your own coding agent at a C program you already have, and it designs a compiler for what you actually wrote — starting from what is already in this one rather than from nothing. What you get back is another binary like the one you are holding: yours, runnable offline, and shareable in exactly the same way.
- Make an account. It is what a compiler gets saved against.
- Connect evolve — the product this compiler came out of — to the agent you already code with. What that involves.
- Point it at a C program and let it tune.
Everything you build stays yours to run without us afterwards. The account is for making compilers, not for using them.