Rewrite

[thetheodor]

This an effort to rewrite dead using diopter. Unfortunately this is a huge change. I wanted to break it down into smaller chunks but I failed :smile: .

Notable changes:

• diopter.compiler.ComplationSetting is now used instead of utils.CompilerSetting. One advantage is that we don't need to pass around a builder in order to use a CompilationSetting as we need an actual compile executable to create one.
• I switched the checker, bisector, reducer, sanitizer to diopter.
• Case is now a RegressionCase, i.e., there's only one good setting. We can later introduce a signature based case that is more flexible.
• The checker is a bit more relaxed: previously it would check that all good settings in a scenario are good potentially missing regressions. Now it is checking only for one of them. This can be extended when we introduce signatures.

There are still a few things left to do before merging this:

• [ ] Test this, while the main pipeline is working fine, I haven't tested reporting etc.
• [ ] Clean up some of the garbage output. A lot of irrelevant stuff is printed when running dead
• [ ] Fix various TODOs
• [ ] Fix diagnose as it is currently broken.

The following are also planned but maybe in a separate PR:

• [ ] Revamp the config. I introduced dead.utils.DeadConfig, a global singelton, where the relevant paths, (e.g., default gcc used for sanitization, compiler repos, builder cache, etc) are stored. Instead of passing this object around it's globally accessible. Maybe it make sense to move some of this to diopter and keep only the dead-specific parts here.
• [ ] Make dead pip-installable
• [ ] Move ccc out of this repo

It probably makes sense to squash most of these commits since there's some transitional code there (e.g., two types of Cases, one with CompilerSetting and one with CompilationSetting)

[Quarub]

Another todo: old_utils should be removed.

[Quarub]

Will the changes be backwards incompatible wrt the DB? If so, I think we can throw away some parts of it.

[thetheodor]

Will the changes be backwards incompatible wrt the DB?

Not really, the new one is much simpler. I'll write a script to convert between them