validate component and declaration naming

[NikLeberg]

related #1463

Context, Motivation & Description

Spinal now checks the names of components and declarations for validity in the currently active language.
If an invalid name is found, it fails the generation.
If an invalid name in another than the currently active language is found, it reports a warning.

Impact on code generation

Spinal will now refuse to generate code that has invalid identifiers. Previously Spinal did just generate it and at a later step the user had to find out (through GHDL, Quartus, etc.) that the generated code was invalid.

Checklist

• Unit tests were added
• API changes are or will be documented: -> no changes to API

[Dolu1990]

Thanks :D

The one thing i'm a bit worrying is the execution overhead of regex.
I realy have no idea how much processing it cost.
Do you have any idea ?

[Readon]

A rough comparison can be carried by testing time of SpinalHDL.
This is normal one.

Here is the one that test time of this PR.

Slightly increase but not that much.

[NikLeberg]

Generally the overhead of the RegEx(es) should be low. It does not use any repeats (i.e. + or * in the pattern) and as such does not have to do backtracking. And backtracking is the costly thing in regex. So it should be fine I guess?

I tried to give a quantitative answer and ran multiple iterations of a Spinal generation, with and without the proposed changes. But the JIT compilation of Scala optimized it so well that it resulted in roughly identical runtimes for both cases. 🤷‍♂️

[Dolu1990]

Thanks ^^

[NikLeberg]

It's a pleasure :)