On Wed, 08 Jan 2014 06:33:39 +0100
why...@f-cpu.org wrote:
from a user point of view, I just need a GHDL that works...
Groovy. A working GHDL is probably the general consensus.
Sure. I think we don't really have the resources to maintain 2 or 3 branches.
I far prefer to have the
It wouldn't hurt to have a wiki page on how to do -2008 features in
ghdl.
Something like:
http://sourceforge.net/p/ghdl-updates/wiki/RoadMap2008/
??? :-)
___
Ghdl-discuss mailing list
Ghdl-discuss@gna.org
On 8 Jan 2014, at 9:34 pm, tging...@free.fr wrote:
It wouldn't hurt to have a wiki page on how to do -2008 features in
ghdl.
Something like:
http://sourceforge.net/p/ghdl-updates/wiki/RoadMap2008/
No something that actually tells how to get the 2008 libraries into a useable
state.
I've been tinkering with the *testsuite* and I've encountered
something curious.
$ ./testsuite.sh 21 | 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
On Wed, 2014-01-08 at 04:47 +0100, tging...@free.fr wrote:
I backported the copyright dates, as an exercise. Then I made a
commit
to the default branch to keep tip attached to default, reducing
the
chance that a commit will happen to 0.31 by mistake...
Hope it looks OK as an
On Wed, 2014-01-08 at 13:03 +1300, David Koontz wrote:
On 8 Jan 2014, at 12:33 pm, Brian Drummond br...@shapes.demon.co.uk wrote:
At last I think I have it...
There are now two branches; ghdl-0.31 and default.
Hope it looks OK as an 0.31 release...
I'll make a source download
On Tue, 2014-01-07 at 23:55 -0500, Adam Jensen wrote:
On Wed, 8 Jan 2014 03:41:37 +0100 (CET)
tging...@free.fr wrote:
On Tue, 07 Jan 2014 23:33:52 +
Brian Drummond br...@shapes.demon.co.uk wrote:
There are now two branches; ghdl-0.31 and default.
I'm not sure whether
On Wed, 2014-01-08 at 04:47 +0100, tging...@free.fr wrote:
I backported the copyright dates, as an exercise. Then I made a
commit
to the default branch to keep tip attached to default,
reducing
the
chance that a commit will happen to 0.31 by mistake...
Hope it looks
On Wed, 2014-01-08 at 05:09 -0500, Adam Jensen wrote:
On Wed, 8 Jan 2014 09:26:50 +0100 (CET)
tging...@free.fr wrote:
I think we don't really have the resources to maintain 2 or 3
branches.
I suspect we need two : release and current. More than that ... I would
agree...
Hmm, can either of
* -RC : when -stable is internally consistent, rigorous testing and
polishing can begin on a Release Candidate snapshot.
Clearly that would be an improvement over the last day or two :-)
Sorry
about that, folks... probably RC1 - release will suffice for ghdl.
Maybe we should re-add
On Wed, 08 Jan 2014 21:06:45 +
Brian Drummond br...@shapes.demon.co.uk wrote:
The usual Mercurial approach to big picture changes is to clone the
entire repo (see www.hginit.com, last chapter) essentially forking the
project for the separate development. It's safer (there is no danger
op
On Wed, 8 Jan 2014 21:54:40 +0100 (CET)
tging...@free.fr 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:
On Wed, 08 Jan 2014 21:06:45 +
Brian Drummond br...@shapes.demon.co.uk wrote:
I suspect we need two : release and current. More than that ... I
would agree...
How about this as a two-branch naming convention? (Old release branches
can be retired). Remember, a naming convention is only
Hello,
On Wed, 8 Jan 2014 21:54:40 +0100 (CET)
tging...@free.fr 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
Hello,
* -RC : when -stable is internally consistent, rigorous testing
and
polishing can begin on a Release Candidate snapshot.
Clearly that would be an improvement over the last day or two :-)
Sorry
about that, folks... probably RC1 - release will suffice for ghdl.
Maybe
On Thu, 9 Jan 2014 06:08:07 +0100 (CET)
tging...@free.fr wrote:
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.
/bin/sh in conjunction with sed and
On Thu, 9 Jan 2014 07:08:44 +0100 (CET)
tging...@free.fr wrote:
So for me (using mcode), ghdl-0.31 is good.
I don't know what mcode represents in this context (obviously not
MATLAB scripts). Have you stopped testing and supporting the gcc
version?
signature.asc
Description: PGP signature
On Thu, 9 Jan 2014 07:08:44 +0100 (CET)
tging...@free.fr wrote:
So for me (using mcode), ghdl-0.31 is good.
I don't know what mcode represents in this context (obviously not
MATLAB scripts). Have you stopped testing and supporting the gcc
version?
mcode is the integrated code generator, which
18 matches
Mail list logo
