Rupert Swarbrick

Hi @cnan123 and thanks for the helpful bug report. This definitely looks wrong to me! :-) @gregac: Is this something you've got time to have a look at?

Hmm, you're right: it doesn't look like that would be easy to do cleanly. A quick hack would be to override `matched_list` to just contain a "test" matching your binary...

For the pyYAML problem, I think you probably just want to use the distro version. See PR #1226.

Oh, I see. I guess `--ignore-installed` makes sense (but possibly with a comment explaining what's going on?)

Possibly a silly question, but is it possible to have reads with "sparse" byte enables? (The top and bottom bytes, but not the ones in the middle). It seems like...

In which case, I guess another option would be to get rid of the byte enables entirely, changing Ibex's LSU to generate requests with size+address instead. Then it's not possible...

In which case, maybe Greg's original suggestion of adding `data_size_o` to the LSU makes the most sense. Then synthesis will throw away the generated byte enable registers if we're connecting...

The problem here is that some of the interrupt/exception tests have historically worked by carefully modelling exactly what should happen. This is a bit brittle and is causing sporadic failures....

Hi there. Thanks for the offer of help. I'd suggest you start with a single file (`verification.rst`, mentioned above, maybe). Reformat to ensure everything is 1 sentence per line, then...

@udinator: Has this now been fixed?