If we used a "Tracer" collection, the name would end up in the printed
output. We implement a function that removes that, so that it looks like
we used one of the normal collections.

We don't need to clean the eventSets if we used the same set at the
previous Spec

Not strictly necessary, since we don't use the generated EventSet in
Experiment. But might be useful later.

This is better because you don't need to allocate ALL the benchmarks
before benchmarking them!

Otherwise, you also have the non-normalized features included, and you'd
have to filter them out when doing the training, which I don't really
want to do.

We want to run with a heap big enough, otherwise we just do garbage collection...

Fixed error reporting

We only print it if there WERE dropped features

We use the checked features in the right places

Prints a more helpful error message, saying what features have been
dropped.

Doesn't work on windows

Instead of changing how features are interpreted depending of whether
they work or not, each feature can check itself if it is supported.

We then have a function which builds a new FeatureSet from an existing
one, filtering out the features that aren't supported.

I also added a method that only returns the features that were mentioned
in the FeatureSet in the map of the results.

We normalize the features by using the existing FeatureRatio, it's just
printed differently.

We don't need to supply a list, the FeatureSet IS a List

Makes the code much cleaner.

HTTP -> SSH

We can actually handle more than 2 counters! So we make sure we do

We just de-activate the counters that are not avaiable.

Some features are about hardware, some are about software. So you need
separate classes to print data with the right types

We'll look into /usr/local/ first.

That PAPI_PATH thing again.

If it now works, it will be the end of years of struggle to get these
damn library.path set!

Instead of trying to manipulate tasks directly, the plugin just sets
and extra property you should have access to.

addCounter should do things the smart way, so we use that.

Had already disabled it before...

Instead of using the SyntheticBenchmarkFeaturePrinter, we can now use
the new API for printing vectors of features. It uses Experiment to get
the features and aggregate them.

SQUASH ME

Depending of the format we use, we'll print different things when
printing to CSV.

If you already obtained the cycles, no need to evaluate it again.

We print the same thing as what the Feature Printer prints

We might want the CostFeature to have the feature we aggregate, but
I used to print "cyclesInsertions", so it makes more sense to me to
constrain it to cycles.

Useful for testing