Florian Mayer

The new approach to optionals could also fairly easy be extended to support nested optionals too. A snippet like ``` Foobar . FooFoo ::= < "-" ":" > "foobar ```...

> BNFC in the rules macro. Exactly. I like your proposed syntax. There are a number of drawbacks even with this solution. 1. A rules macro containing `n` optional symbols...

> But it seems that what you want to do is to be able to reuse a grammar written in a different formalism, maybe ebnf? Yes, I already stated that...

I just ran into this issue with a stencil PE synthesized by Vivado HLS that deadlocks the whole system. The code in question looks like this: ```c void tlf(float *buf1,...

Hi @sommerlukas, thank you for your quick reply. > How many PEs do you have in your design? Just one, syntheisized with Vivado HLS 2018.2 used in a TaPaSCo composition...

Thank you @wirthjohannes and @sommerlukas for your help. I will investigate that issue further and will add some of my insights here.

Okay, short summary what I have found out so far: In multi port designs, such as `void tlf(float *buf1, float *buf2)`, where both ports are bundled onto an AXI master...

I first tried out `pragma`s and various TCL commands but sadly none of them had the desired effect. Then I replaced array subscripts by calls to these two functions: ```c...

Suggestion for new command line features: - Option for the location of the `compose` directory. `--composeDir` - Option for a copy of the bistream `-o ~/path/to/optional/bitstream/copy.bit The latter will be...

I can take care of `-o`