Quartus Extensions

[bo3z]

A# Description

📝 Support for custom Keras and HLS layers

• Simple re-ordering of optimizers in the Quartus backend allows to register a new layer function/config template, alongside any optimizers linked to it.

Type of change

For a new feature or function, please create an issue first to discuss it
with us before submitting a pull request.

Note: Please delete options that are not relevant.

• Bug fix (non-breaking change that fixes an issue) - This should have worked before in a similar manner way to Vivado, but was never tested. This PR simply adds a PyTest and fixed flow requirements to allow custom Keras layers to be introduced.

Tests

• Expanded test/pytest/test_extensions.py to include Quartus (on top of Vivado)

Checklist

• I have read the guidelines for contributing.
• [] I have commented my code, particularly in hard-to-understand areas.
• [] I have made corresponding changes to the documentation.
• My changes generate no new warnings.
• I have added tests that prove my fix is effective or that my feature works.B

[vloncar]

Does this line cause problems for Intel HLS compiler? What if we wrap it in #ifdef __SYNTHESIS__ and do similar for Intel compiler

[bo3z]

I think it won't (I think there is a flag for ignoring unknown pragmas), but PyTests do not run HLS synthesis anyway, so this line does not really do anything. Only reason I removed it is to make it "technically" correct.

[vloncar]

That entire file used to be an example of extensions API that also served as a test, so that block is an example of (Vivado) HLS code that users should write themselves. I don't see how distilling it to pure C++ code makes it "tecnhically" correct ;-) But it doesn't matter, since now it is a test that serves as a (slightly convoluted) example.