Hello,

> On Wed, 8 Jan 2014 21:54:40 +0100 (CET)
> [email protected] wrote:
> > > 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
> > 
> > Weird, as I don't have this issue.
> > 
> 
> Test: 375 definitely fails on FreeBSD-9.2(i386) with:
> 
> $ hg branch
> ghdl-0.31
> 
> I think I did an "hg pull; hg update -r ghdl-0.31" around 3PM EST
> today and I followed the FreeBSD "-alt" [build instructions][1].
> 
> [1]:
> http://sourceforge.net/p/ghdl-updates/wiki/FreeBSD%20Instructions/

Interesting.  I have tested with ghdl_mcode, no failure here.
Maybe a mcode vs gcc issue ?

> > > tests (?). Is there a convenient method to run all of the tests
> > > (regardless of failures) then generate a [comprehensive] report?
> > 
> > No, but the driver (testsuite.sh) is very simple, so you can modify
> > it
> > to fit your need.
> > 
> 
> Are modifications to the test [and report generation] suite something
> that could be shared with the community?

Sure, this is an open-source project.

> Is perl sufficiently
> ubiquitous to be used in scripts or would everyone prefer to keep the
> dependencies simple (/bin/sh)?

I don't like perl, so I prefer to avoid it (and I only have a basic perl
knowledge).
If you need something more elaborate than sh, what about python ?

To be discussed with the community.

It would be nice to have a parallel run of the test suite, and for sure
/bin/sh is not the right tool for that.

Tristan.

_______________________________________________
Ghdl-discuss mailing list
[email protected]
https://mail.gna.org/listinfo/ghdl-discuss

Reply via email to