Support tracking: GHDL [VHDL-2008]

[eine]

The purpose of this issue is to track bugs reported to maintainers of GHDL regarding compliance with these test suites.

• vhdl_2008/tb_condition_operator.vhd
  • [Compliance-Tests] Condition operators for type bit ghdl/ghdl#977
• vhdl_2008/tb_matching_operator.vhd
  • [Compliance-Tests] vhdl_2008/tb_matching_operator crash during analysis ghdl/ghdl#1063
• vhdl_2008/tb_entity_generic_type.vhd
  • [Compliance-Tests] Analysing vhdl_2008/tb_entity_generic_type.vhd crashes ghdl/ghdl#2365

[eine]

As commented in ghdl/ghdl#1063, most matching operators (?/=, ?<, ?<=, ?>, ?>=) are not implemented in GHDL yet but the equality operator is available.

Unfortunately, 2 of the 8 related tests in tb_matching_operator.vhd fail with the current implementation because of some weird interaction between VUnit and GHDL. A workaround, which is shown in https://github.com/VHDL/Compliance-Tests/tree/ghdl-matchingop, is to explicitly set the type of 'H' and 'W'. @LarsAsplund, what do you think? Should we ensure that the signals/variables that are compared are explicitly of type std_logic? It was "a stupid mistake" (ghdl/ghdl#1063 (comment)).