GCHQDeveloper560

I took a first pass at converting Quartus to use the command generator. First, it has a case that uses multiple commands to generate a target, so I've added this...

The failing tests are unrelated to this work. See #254 for a reporting test that works with the new Pandas 1.3. I rebased this branch on top of that one...

I recently experimented with DPI in ModelSim, so this would be nice to have! Thanks! The build logs have expired to see exactly why the tests checks failed, but I...

As discussed in #251 the command generator should probably also support cases where multiple commands need to be run to generate a target. I'm less sure whether variables should be...

The tests don't need the actual tools and instead use mock versions of the tools in `tests/mock_commands`. The GitHub CI setup is just Ubuntu without anything special installed, and tests...

The test failures print the name of the temporary directory used for the output, so you shouldn't have to dive into Python to check the test's output files. In the...

Would you expect each backend class to have reporting methods, or would they be colocated in an `edalize.reporting` module? Would you expect to grab every table in a report, or...

It might be nice to have a common device-neutral table with some basic information, but is it going to be too painful to map device-specific resources to a common format?...

There's an initial shot at reporting resource and timing information for ISE, Vivado, and Quartus, at least for some devices, at [my fork](https://github.com/GCHQDeveloper560/edalize/tree/reporting). In addition to the detailed device-specific information...

@mithro, @kgugala: I appreciated your original pointer to SymbiFlow/fpga-tool-perf. It's where I'd gotten the "extract all the tables" approach versus my previous report parsing that had just gone in and...