Rob Springer

I have a test proc : ``` #[test_proc()] proc Proc { terminator: chan out; bar: chan out; config(terminator: chan out) { let (foo, baa) = chan; (terminator, bar) } next(tok:...

In the IR, you can't select between two tokens, e.g. a one-hot select whose options are tokens. In DSLX, though, the following is currently allowed: ``` let tok = if...

DSLX: Can't declare array of ColonRef type

1

Behold: ``` let ctr_cmds = aes_ctr[u32:4]:[ aes_ctr::initial_state().command, ...]; ``` results in ``` 0093: let ctr_cmds = aes_ctr[u32:4]:[ aes_ctr::initial_state().command, ...]; ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^^ ParseError: Expected ';', got ':' ``` Whereas ``` type asdf...

For example, consider an AXI slave interface, which has (among others) the read transaction ports ARADDR, ARSIZE, ARLEN, and ARBURST, all protected by the pair ARVALID and ARREADY. I could...

I have a chunk of IR that's slowwwwwwwwww to compile and a 40-some core machine. Having to wait 40 * a long time for the threads to start up is...

Ex: for some AES work, I need to specify channel FIFO depths to get through proc inlining.

I've found that it'd be useful to only conditionally output logging messages (e.g., on FSM state).

Currently, the only ConstantDef nodes we generate use Number nodes for values. We recently encountered an error in DSLX->IR conversion related to constants defined via invocations & other operations. It'd...

Lower arrays of channels from DSLX into IR

3

DSLX currently supports declaring and using arrays of channels, e.g., `let (ps, cs) = chan[4];`, but these aren't currently lowerable to IR. Sadly, it's not a trivial task to do...

...right now, trace! operations are printed during constexpr eval, resulting in 2x trace output. Plz only do 1x.