@zerkman You mean, the fact that it does not seem to know about `ila_0` (or for that matter `work.ila_0`) causes it to ignore the whole rest?

I did not think of that, but it's in fact what `vdhl_ls` does as well. And for a different entity (which is in component/instantiation, i.e. pre-2008 grammar) it does identify the faulty line.

So, I might have been a bit harsh here. Still: the resulting error messages are like version python's in the pre 2010s. Cryptic and misleading at best.

@cweickhmann I haven't been using Vivado's editor for a long time (using an external editor instead), but IIRC if you hover the mouse cursor over the squiggly-red underlined text line, it should display the actual error message. It could be about missing ila_0 indeed, if the syntax checker is somehow faulty in accessing the ila_0 definition.

@zerkman Yup, that's the case.

I was just very angry because the elaborate/linter error messages pointed into a completely different direction.

Imho the Vivado editor is utterly unusable (for other but plenty of reasons).

I am using KDE Kate with `vhdl_ls` (a rust language server spin-off, if I'm not mistaken) and I'm happy with it. Although that combo did not spot the error either. And for the same reason. But it does not know about Xilinx's libraries. Vivado should know better (and yeah, it's partly my fault because I hate component/instantiation ^^).