I've been tinkering with the *testsuite* and I've encountered something curious.
$ ./testsuite.sh 2>&1 | tee testsuite.log [...lots of output...] The testing process ends with: Test: 375 ghdl -a --std=93c vhdl-93/ashenden/compliant/ch_13_fg_13_26.vhd vhdl-93/ashenden/compliant/ch_13_fg_13_26.vhd:33:20: port "a" already associated in primary binding vhdl-93/ashenden/compliant/ch_13_fg_13_26.vhd:33:28: port "c" already associated in primary binding vhdl-93/ashenden/compliant/ch_13_fg_13_26.vhd:33:36: port "b" already associated in primary binding vhdl-93/ashenden/compliant/ch_13_fg_13_26.vhd:33:44: port "y" already associated in primary binding ghdl: compilation error I'm not sure I would choose to use a [VHDL] configuration to remap the ports of an instantiated component that way (ch_13_fg_13_26). However, I guess that's part of the current standard and these are compliance tests (?). Is there a convenient method to run all of the tests (regardless of failures) then generate a [comprehensive] report?
signature.asc
Description: PGP signature
_______________________________________________ Ghdl-discuss mailing list [email protected] https://mail.gna.org/listinfo/ghdl-discuss
