Issues #3862, #3863: Typespec assignment problems

[hs-apotell]

Issues #3862, #3863: Typespec assignment problems

• Handle "returnTypespec" param correctly
• Set Typespec when handling io_decls
• Handle packed_array_typespec as well when handling array_tyespec

[hs-apotell]

@alaindargelas Two tests (CoreSweRV & Opentitan) are reporting one additional error (Unresolved hierarchical path) each. I tried investigating but didn't have much luck. You might have to spend some time investigating this.

[alaindargelas]

@hs-apotell , something is missing in this PR.
Can you first create a PR in UHDM?

[hs-apotell]

@hs-apotell , something is missing in this PR. Can you first create a PR in UHDM?

Sorry, missed the UHDM PR. Here it is chipsalliance/UHDM#1021

[alaindargelas]

@alaindargelas Two tests (CoreSweRV & Opentitan) are reporting one additional error (Unresolved hierarchical path) each. I tried investigating but didn't have much luck. You might have to spend some time investigating this.

The new error is "correct",
it comes from this code:

Surelog/third_party/UVM/1800.2-2017-1.0/src/base/uvm_phase.svh

Line 1774 in afe293a

foreach (pred.m_predecessors[next_pred])

Surelog is not capable of finding the right type for the foreach loop index "pred".

[alaindargelas]

The message is bad though: [ERR:UH0725] Unresolved hierarchical reference "".
Because the hier_path object has no file, line nor name information.

[hs-apotell]

The message is bad though: [ERR:UH0725] Unresolved hierarchical reference "".

I didn't change anything on how the error gets reported. I can look into it.

[alaindargelas]

We would look at the place the hier_path object is built, thats were it's missing the populate data