iverilog-devel — Conversations on matters of Icarus Verilog development

Re: [Iverilog-devel] Small stuff

[Evan L. <sa2...@cy...>]

Great - thanks. Seems strange that this was changed from 2001 to 2005.

Re: [Iverilog-devel] Small stuff

[Martin W. <ic...@ma...>]

On 03/10/2020 08:08, Evan Lavelle wrote:
> On 01/10/2020 14:47, Martin Whitaker wrote:
> 
>> Can you give an example of this.
> 
> Ok, worked it out: if the task is declared with brackets around the
> formals, but there are no formals, then a warning is raised. If the task
> is declared without brackets, then no warning is raised.
> 
> I guess the square brackets around 'task_port_list' below weren't noticed?
> 
> -E
> 
> task_declaration ::= (From A.2.7)
>      task [ automatic ] task_identifier ;
>        { task_item_declaration }
>        statement_or_null
>        endtask
>    | task [ automatic ] task_identifier ( [ task_port_list ] ) ;
>        { block_item_declaration }
>        statement_or_null
>      endtask

That warning was added in this commit:

commit 46350da5f0f3c623cb9fe05003d7e2b8506d14a7
Author: Cary R <cy...@ya...>
Date:   Fri Apr 3 18:55:48 2009 -0700

     Add support for empty task port lists with a warning.

     The standard does not allow this, but it appears that other
     simulators do. This patch adds the functionality, but prints
     a warning message for the invalid task definition.

so it seems your guess is correct, unless Cary was looking at the 2001 
standard, which doesn't make task_port_list optional.

I've fixed this in both the master and v11 branches. The warning is now 
only issued if you select a Verilog language generation < 2005.

Re: [Iverilog-devel] Small stuff

[Evan L. <sa2...@cy...>]

On 01/10/2020 14:47, Martin Whitaker wrote:

> Can you give an example of this.

Ok, worked it out: if the task is declared with brackets around the
formals, but there are no formals, then a warning is raised. If the task
is declared without brackets, then no warning is raised.

I guess the square brackets around 'task_port_list' below weren't noticed?

-E

task_declaration ::= (From A.2.7)
    task [ automatic ] task_identifier ;
      { task_item_declaration }
      statement_or_null
      endtask
  | task [ automatic ] task_identifier ( [ task_port_list ] ) ;
      { block_item_declaration }
      statement_or_null
    endtask

Re: [Iverilog-devel] Debian/Ubuntu package maintainers

[Cary R. <cy...@ya...>]

 You probably know someone who can compile the latest version from source :-).
Cary

    On Friday, October 2, 2020, 8:49:56 AM PDT, Stephen Williams <st...@ic...> wrote:  
 
 I stand corrected. Good!
The bad news is that my work computer is Ubuntu 18:-(
On Thu, Oct 1, 2020 at 10:48 PM Cary R. via Iverilog-devel <ive...@li...> wrote:

 This link shows that Debian is at 10.3: Debian Package Tracker - iverilog

| 
| 
|  | 
Debian Package Tracker - iverilog


 |

 |

 |



and this link shows Ubuntu also at 10.3: Ubuntu – Details of package iverilog in groovy

| 
| 
| 
|  |  |

 |

 |
| 
|  | 
Ubuntu – Details of package iverilog in groovy

Icarus verilog compiler
 |

 |

 |



Cary


    On Thursday, October 1, 2020, 9:58:55 PM PDT, Stephen Williams <st...@ic...> wrote:  
 
 By any chance are the package maintainers for debian/ubuntu on this
list? I'm asking because apparently Ubuntu is still on 10.1 and this
is a system I'd like to see catch up to the latest.

-- 
Steve Williams                "The woods are lovely, dark and deep.
st...@ic...              But I have promises to keep,
http://www.icarus.com         and lines to code before I sleep,
http://www.picturel.com       And lines to code before I sleep."


_______________________________________________
Iverilog-devel mailing list
Ive...@li...
https://lists.sourceforge.net/lists/listinfo/iverilog-devel
  _______________________________________________
Iverilog-devel mailing list
Ive...@li...
https://lists.sourceforge.net/lists/listinfo/iverilog-devel



-- 
Steve Williams                "The woods are lovely, dark and deep.
st...@ic...              But I have promises to keep,
http://www.icarus.com         and lines to code before I sleep,
http://www.picturel.com       And lines to code before I sleep."_______________________________________________
Iverilog-devel mailing list
Ive...@li...
https://lists.sourceforge.net/lists/listinfo/iverilog-devel
  

Re: [Iverilog-devel] Debian/Ubuntu package maintainers

[Stephen W. <st...@ic...>]

I stand corrected. Good!

The bad news is that my work computer is Ubuntu 18:-(

On Thu, Oct 1, 2020 at 10:48 PM Cary R. via Iverilog-devel <
ive...@li...> wrote:

> This link shows that Debian is at 10.3: Debian Package Tracker - iverilog
> <https://tracker.debian.org/pkg/iverilog>
>
> Debian Package Tracker - iverilog
>
> <https://tracker.debian.org/pkg/iverilog>
>
>
> and this link shows Ubuntu also at 10.3: Ubuntu – Details of package
> iverilog in groovy <https://packages.ubuntu.com/groovy/iverilog>
>
> Ubuntu – Details of package iverilog in groovy
>
> Icarus verilog compiler
> <https://packages.ubuntu.com/groovy/iverilog>
>
>
> Cary
>
>
> On Thursday, October 1, 2020, 9:58:55 PM PDT, Stephen Williams <
> st...@ic...> wrote:
>
>
> By any chance are the package maintainers for debian/ubuntu on this
> list? I'm asking because apparently Ubuntu is still on 10.1 and this
> is a system I'd like to see catch up to the latest.
>
> --
> Steve Williams                "The woods are lovely, dark and deep.
> st...@ic...              But I have promises to keep,
> http://www.icarus.com         and lines to code before I sleep,
> http://www.picturel.com       And lines to code before I sleep."
>
>
> _______________________________________________
> Iverilog-devel mailing list
> Ive...@li...
> https://lists.sourceforge.net/lists/listinfo/iverilog-devel
> _______________________________________________
> Iverilog-devel mailing list
> Ive...@li...
> https://lists.sourceforge.net/lists/listinfo/iverilog-devel
>


-- 
Steve Williams                "The woods are lovely, dark and deep.
st...@ic... <ste...@gm...>              But I have promises
to keep,
http://www.icarus.com         and lines to code before I sleep,
http://www.picturel.com       And lines to code before I sleep."

Re: [Iverilog-devel] Small stuff

[Evan L. <sa2...@cy...>]

On 01/10/2020 14:47, Martin Whitaker wrote:

> 
>> 2 - Under some circumstances, a task with no parameters will raise a
>> compiler warning; in some circumstances, it won't. It would be nice to
>> get rid of this warning as well - it serves no purpose.
> 
> Can you give an example of this.

Unfortunately, I can't. I've noticed this in a file I've been working on
for the last few days, and sometimes it's there, and sometimes it isn't,
presumably depending on the contents of the rest of the file. I'll keep
an eye out and post an example if I can get it again.

Re: [Iverilog-devel] Debian/Ubuntu package maintainers

[Cary R. <cy...@ya...>]

 This link shows that Debian is at 10.3: Debian Package Tracker - iverilog

| 
| 
|  | 
Debian Package Tracker - iverilog


 |

 |

 |



and this link shows Ubuntu also at 10.3: Ubuntu – Details of package iverilog in groovy

| 
| 
| 
|  |  |

 |

 |
| 
|  | 
Ubuntu – Details of package iverilog in groovy

Icarus verilog compiler
 |

 |

 |



Cary


    On Thursday, October 1, 2020, 9:58:55 PM PDT, Stephen Williams <st...@ic...> wrote:  
 
 By any chance are the package maintainers for debian/ubuntu on this
list? I'm asking because apparently Ubuntu is still on 10.1 and this
is a system I'd like to see catch up to the latest.

-- 
Steve Williams                "The woods are lovely, dark and deep.
st...@ic...              But I have promises to keep,
http://www.icarus.com         and lines to code before I sleep,
http://www.picturel.com       And lines to code before I sleep."


_______________________________________________
Iverilog-devel mailing list
Ive...@li...
https://lists.sourceforge.net/lists/listinfo/iverilog-devel
  

[Iverilog-devel] Debian/Ubuntu package maintainers

[Stephen W. <st...@ic...>]

By any chance are the package maintainers for debian/ubuntu on this
list? I'm asking because apparently Ubuntu is still on 10.1 and this
is a system I'd like to see catch up to the latest.

-- 
Steve Williams                "The woods are lovely, dark and deep.
st...@ic...              But I have promises to keep,
http://www.icarus.com         and lines to code before I sleep,
http://www.picturel.com       And lines to code before I sleep."

Re: [Iverilog-devel] Small stuff

[Martin W. <ic...@ma...>]

On 01/10/2020 10:02, Evan Lavelle wrote:
> A couple of minor irritations:
> 
> 1 - a genvar has a size which is calculated dynamically by Icarus; it
> might be 5 bits, or 10 bits, or whatever. This is fine, but when you
> connect it to a module port there's nothing you can declare the port as
> that won't generate a compiler warning (unless you guess or derive the
> correct size, of course). So, you can't generally declare the port as
> '[31:0]', for example

This should have been avoidable by using the -gstrict-expr-width 
compiler option, but this particular case wasn't handled. I've pushed a 
fix for that to both the master and v11 branches.

> 2 - Under some circumstances, a task with no parameters will raise a
> compiler warning; in some circumstances, it won't. It would be nice to
> get rid of this warning as well - it serves no purpose.

Can you give an example of this.

[Iverilog-devel] Small stuff

[Evan L. <sa2...@cy...>]

A couple of minor irritations:

1 - a genvar has a size which is calculated dynamically by Icarus; it
might be 5 bits, or 10 bits, or whatever. This is fine, but when you
connect it to a module port there's nothing you can declare the port as
that won't generate a compiler warning (unless you guess or derive the
correct size, of course). So, you can't generally declare the port as
'[31:0]', for example

2 - Under some circumstances, a task with no parameters will raise a
compiler warning; in some circumstances, it won't. It would be nice to
get rid of this warning as well - it serves no purpose.

-Evan

Re: [Iverilog-devel] Icarus Verilog Release 11.0

[Galen S. <ga...@se...>]

On 9/27/20 9:33 AM, Stephen Williams wrote:
> Oh, you did that. Hm.
> What's in your version_base.h? That should be managed by git.

[galens@toto iverilog]$ git log -1 version_base.h
commit 84b4ebee0cfcda28a242d89a07020cd70b1d3e7f (HEAD, tag: v11_0, origin/v11-branch)
Author: Stephen Williams <st...@ic...>
Date:   Sat Sep 26 15:44:25 2020 -0700

    Mark version as stable.
[galens@toto iverilog]$ cat version_base.h 
#ifndef VERSION
/*
 * Edit this definition in version_base.in to define the base version
 * number for the compiled result.
 */
# define VERSION_MAJOR  11
# define VERSION_MINOR   0

/*
 * This will be appended to the version. Use this to mark development
 * versions and the like.
 */
# define VERSION_EXTRA   " (stable)"

# define VERSION_STRINGIFY(x) #x
# define VERSION_STR(a,b,extra) VERSION_STRINGIFY(a.b) extra

#define VERSION VERSION_STR(VERSION_MAJOR,VERSION_MINOR,VERSION_EXTRA)
#endif


I'm guessing the problem is that version_tag.h is stale and needs
to be deleted.  make distclean does not delete it.  That appears
to be intentional, as per the distclean target in Makefile.in.

distclean: clean
        $(foreach dir,$(SUBDIRS),$(MAKE) -C $(dir) $@ && ) true
        $(foreach dir,$(NOTUSED),$(MAKE) -C $(dir) $@ && ) true
        rm -f Makefile config.status config.log config.cache
        rm -f stamp-config-h config.h
        rm -f stamp-_pli_types-h _pli_types.h
ifneq (@srcdir@,.)
        rm -f version_tag.h check.conf
        rmdir $(SUBDIRS) $(NOTUSED)
endif


Perhaps a release build is only meant to be done from a clone
into a new directory.


galen
-- 
Galen Seitz
ga...@se...

Re: [Iverilog-devel] Icarus Verilog Release 11.0

[Stephen W. <st...@ic...>]

Oh, you did that. Hm.
What's in your version_base.h? That should be managed by git.

On Sun, Sep 27, 2020 at 9:32 AM Stephen Williams <st...@ic...> wrote:
>
> Try "make version" to force the version_tag.h to rebuild.
>
> On Sun, Sep 27, 2020 at 9:13 AM Galen Seitz <ga...@se...> wrote:
> >
> > On 9/27/20 8:58 AM, Stephen Williams wrote:
> > > The version should report 11.0 (stable). You are still on the master branch?
> >
> > I did a git fetch, followed by a git checkout v11_0.  HEAD is at commit
> > 84b4ebee.
> >
> > 84b4ebee (HEAD, tag: v11_0, origin/v11-branch) Mark version as stable.
> >
> > When I do a make distclean at the top level, version_tag.h is not
> > removed, so it is stale.  I must be missing some step in the build
> > process.  Here's what I did to build.
> >
> > git fetch
> > git checkout v11_0
> > make distclean
> > sh autoconf.sh
> > ./configure
> > make version    # reports `version' is up to date.
> > make -j8 &> make.log
> > make check
> > driver/iverilog -V
> >
> >
> > galen
> > --
> > Galen Seitz
> > ga...@se...
> >
> >
> > _______________________________________________
> > Iverilog-devel mailing list
> > Ive...@li...
> > https://lists.sourceforge.net/lists/listinfo/iverilog-devel
>
>
>
> --
> Steve Williams                "The woods are lovely, dark and deep.
> st...@ic...              But I have promises to keep,
> http://www.icarus.com         and lines to code before I sleep,
> http://www.picturel.com       And lines to code before I sleep."



-- 
Steve Williams                "The woods are lovely, dark and deep.
st...@ic...              But I have promises to keep,
http://www.icarus.com         and lines to code before I sleep,
http://www.picturel.com       And lines to code before I sleep."

Re: [Iverilog-devel] Icarus Verilog Release 11.0

[Stephen W. <st...@ic...>]

Try "make version" to force the version_tag.h to rebuild.

On Sun, Sep 27, 2020 at 9:13 AM Galen Seitz <ga...@se...> wrote:
>
> On 9/27/20 8:58 AM, Stephen Williams wrote:
> > The version should report 11.0 (stable). You are still on the master branch?
>
> I did a git fetch, followed by a git checkout v11_0.  HEAD is at commit
> 84b4ebee.
>
> 84b4ebee (HEAD, tag: v11_0, origin/v11-branch) Mark version as stable.
>
> When I do a make distclean at the top level, version_tag.h is not
> removed, so it is stale.  I must be missing some step in the build
> process.  Here's what I did to build.
>
> git fetch
> git checkout v11_0
> make distclean
> sh autoconf.sh
> ./configure
> make version    # reports `version' is up to date.
> make -j8 &> make.log
> make check
> driver/iverilog -V
>
>
> galen
> --
> Galen Seitz
> ga...@se...
>
>
> _______________________________________________
> Iverilog-devel mailing list
> Ive...@li...
> https://lists.sourceforge.net/lists/listinfo/iverilog-devel



-- 
Steve Williams                "The woods are lovely, dark and deep.
st...@ic...              But I have promises to keep,
http://www.icarus.com         and lines to code before I sleep,
http://www.picturel.com       And lines to code before I sleep."

Re: [Iverilog-devel] Icarus Verilog Release 11.0

[Galen S. <ga...@se...>]

On 9/27/20 8:58 AM, Stephen Williams wrote:
> The version should report 11.0 (stable). You are still on the master branch?

I did a git fetch, followed by a git checkout v11_0.  HEAD is at commit 
84b4ebee.

84b4ebee (HEAD, tag: v11_0, origin/v11-branch) Mark version as stable.

When I do a make distclean at the top level, version_tag.h is not 
removed, so it is stale.  I must be missing some step in the build 
process.  Here's what I did to build.

git fetch
git checkout v11_0
make distclean
sh autoconf.sh
./configure
make version	# reports `version' is up to date.
make -j8 &> make.log
make check
driver/iverilog -V


galen
-- 
Galen Seitz
ga...@se...

Re: [Iverilog-devel] Icarus Verilog Release 11.0

[Stephen W. <st...@ic...>]

The version should report 11.0 (stable). You are still on the master branch?

On Sun, Sep 27, 2020 at 8:41 AM Galen Seitz <ga...@se...> wrote:
>
> On 9/26/20 1:59 PM, Stephen Williams wrote:
> > I've made an 11.0 release, and the release source files are here:
> >
> > <ftp://ftp.icarus.com/pub/eda/verilog/v11/>
> >
> > Try it out, and let's see how it goes. Feedback in this mailing list,
> > especially with packaging issues.
> >
>
> FWIW, I was able to successfully build and run make check from the v11_0
> tag under CentOS 7, which has gcc 4.8.5.
>
> driver/iverilog -V shows:
> Icarus Verilog Parser/Elaborator version 11.0 (devel) (v10_2-78-gb7b22660)
>
> I have no need to build a release, but what is the correct method for
> updating version_tag.h?  Running make distclean did not remove it, so
> it remains unchanged from my original build many months ago.
>
>
> Again FWIW, I noticed that the build generated several warnings.
>
> [galens@toto iverilog]$ grep warning make.log |uniq
> netqueue.cc:25:52: warning: declaration of ‘max_idx’ shadows a member of 'this' [-Wshadow]
> net_nex_input.cc:267:17: warning: declaration of ‘func’ shadows a member of 'this' [-Wshadow]
> net_scope.cc:234:73: warning: declaration of ‘type’ shadows a member of 'this' [-Wshadow]
> parse.cc:8456:18: warning: missing initializer for member ‘vlltype::text’ [-Wmissing-field-initializers]
> lexor.cc:1912:13: warning: unused parameter ‘yyscanner’ [-Wunused-parameter]
> lexor.cc:2232:7: warning: unused parameter ‘yyscanner’ [-Wunused-parameter]
> lexor.cc:2237:7: warning: unused parameter ‘yyscanner’ [-Wunused-parameter]
> lexor.cc:2249:6: warning: unused parameter ‘yyscanner’ [-Wunused-parameter]
> vvp_net_sig.h:333:53: warning: declaration of ‘size’ shadows a member of 'this' [-Wshadow]
> vvp_net_sig.cc:714:65: warning: declaration of ‘size’ shadows a member of 'this' [-Wshadow]
> vvp_net_sig.cc:746:65: warning: declaration of ‘size’ shadows a member of 'this' [-Wshadow]
> vvp_net_sig.h:333:53: warning: declaration of ‘size’ shadows a member of 'this' [-Wshadow]
> getp.c:55:12: warning: cast from pointer to integer of different size [-Wpointer-to-int-cast]
>
>
> galen
> --
> Galen Seitz
> ga...@se...
>
>
> _______________________________________________
> Iverilog-devel mailing list
> Ive...@li...
> https://lists.sourceforge.net/lists/listinfo/iverilog-devel



-- 
Steve Williams                "The woods are lovely, dark and deep.
st...@ic...              But I have promises to keep,
http://www.icarus.com         and lines to code before I sleep,
http://www.picturel.com       And lines to code before I sleep."

Re: [Iverilog-devel] Icarus Verilog Release 11.0

[Galen S. <ga...@se...>]

On 9/26/20 1:59 PM, Stephen Williams wrote:
> I've made an 11.0 release, and the release source files are here:
> 
> <ftp://ftp.icarus.com/pub/eda/verilog/v11/>
> 
> Try it out, and let's see how it goes. Feedback in this mailing list,
> especially with packaging issues.
> 

FWIW, I was able to successfully build and run make check from the v11_0
tag under CentOS 7, which has gcc 4.8.5.

driver/iverilog -V shows:
Icarus Verilog Parser/Elaborator version 11.0 (devel) (v10_2-78-gb7b22660)

I have no need to build a release, but what is the correct method for
updating version_tag.h?  Running make distclean did not remove it, so
it remains unchanged from my original build many months ago.


Again FWIW, I noticed that the build generated several warnings.

[galens@toto iverilog]$ grep warning make.log |uniq
netqueue.cc:25:52: warning: declaration of ‘max_idx’ shadows a member of 'this' [-Wshadow]
net_nex_input.cc:267:17: warning: declaration of ‘func’ shadows a member of 'this' [-Wshadow]
net_scope.cc:234:73: warning: declaration of ‘type’ shadows a member of 'this' [-Wshadow]
parse.cc:8456:18: warning: missing initializer for member ‘vlltype::text’ [-Wmissing-field-initializers]
lexor.cc:1912:13: warning: unused parameter ‘yyscanner’ [-Wunused-parameter]
lexor.cc:2232:7: warning: unused parameter ‘yyscanner’ [-Wunused-parameter]
lexor.cc:2237:7: warning: unused parameter ‘yyscanner’ [-Wunused-parameter]
lexor.cc:2249:6: warning: unused parameter ‘yyscanner’ [-Wunused-parameter]
vvp_net_sig.h:333:53: warning: declaration of ‘size’ shadows a member of 'this' [-Wshadow]
vvp_net_sig.cc:714:65: warning: declaration of ‘size’ shadows a member of 'this' [-Wshadow]
vvp_net_sig.cc:746:65: warning: declaration of ‘size’ shadows a member of 'this' [-Wshadow]
vvp_net_sig.h:333:53: warning: declaration of ‘size’ shadows a member of 'this' [-Wshadow]
getp.c:55:12: warning: cast from pointer to integer of different size [-Wpointer-to-int-cast]


galen
-- 
Galen Seitz
ga...@se...

Re: [Iverilog-devel] Icarus Verilog Release 11.0

[Martin W. <ic...@ma...>]

The Windows installer provided by Pablo Bleyer includes the necessary 
DLLs and will install them alongside iverilog. Those building from 
source will have to install mingw-w64 and msys2 anyway. The build 
instructions on the Wiki do mention the need to add the DLLs to the path 
or to copy them into the install directory.

On 27/09/2020 12:34, Evan Lavelle wrote:
> See the attached log for warnings on mingw32, gcc 9.1.0. The build
> completes Ok, and all my own regressions pass.
> 
> There is a problem, though, which is that the build is dynamic. On my
> Win10 box I need to find the mingw32 libgcc_s_dw2-1.dll,
> libstdc++-6.dll, and libwinpthread-1.dll, and add them to the Icarus bin
> directory. In practice, that may mean that Windows users have to do an
> msys2 and mingw32 install and copy over their own local versions, which
> isn't realistic, and is going to stop people using Icarus on Windows. I
> thought I put something on the wiki about this last year but I can't
> find it.
> 
> The solution is simple - it needs to be built as a static 32-bit
> executable for Windows, but this could be several hours work. I'll have
> a think about this when I get some time.
> 
> 
> 
> _______________________________________________
> Iverilog-devel mailing list
> Ive...@li...
> https://lists.sourceforge.net/lists/listinfo/iverilog-devel
> 

Re: [Iverilog-devel] Icarus Verilog Release 11.0

[Evan L. <sa2...@cy...>]

See the attached log for warnings on mingw32, gcc 9.1.0. The build
completes Ok, and all my own regressions pass.

There is a problem, though, which is that the build is dynamic. On my
Win10 box I need to find the mingw32 libgcc_s_dw2-1.dll,
libstdc++-6.dll, and libwinpthread-1.dll, and add them to the Icarus bin
directory. In practice, that may mean that Windows users have to do an
msys2 and mingw32 install and copy over their own local versions, which
isn't realistic, and is going to stop people using Icarus on Windows. I
thought I put something on the wiki about this last year but I can't
find it.

The solution is simple - it needs to be built as a static 32-bit
executable for Windows, but this could be several hours work. I'll have
a think about this when I get some time.

Re: [Iverilog-devel] Icarus Verilog Release 11.0

[Stephen W. <st...@ic...>]

Probably a good idea for me to make it report as 11.0 (stable) to
follow the existing pattern. In fact, done. I've updated the files and
the tag. There's always some little thing like this :-(

On Sat, Sep 26, 2020 at 3:24 PM Martin Whitaker
<ic...@ma...> wrote:
>
> On 26/09/2020 21:59, Stephen Williams wrote:
> > I've made an 11.0 release, and the release source files are here:
> >
> > <ftp://ftp.icarus.com/pub/eda/verilog/v11/>
> >
> > Try it out, and let's see how it goes. Feedback in this mailing list,
> > especially with packaging issues.
> >
> I tested a clean checkout and build of the v11-branch. The version is
> reported as "11.0". Previous releases would report something like "10.3
> (stable)". The lack of a space after the version number caused the
> vpi/check_version test to segfault. I've fixed that.
>
>
> _______________________________________________
> Iverilog-devel mailing list
> Ive...@li...
> https://lists.sourceforge.net/lists/listinfo/iverilog-devel



-- 
Steve Williams                "The woods are lovely, dark and deep.
st...@ic...              But I have promises to keep,
http://www.icarus.com         and lines to code before I sleep,
http://www.picturel.com       And lines to code before I sleep."

Re: [Iverilog-devel] Icarus Verilog Release 11.0

[Martin W. <ic...@ma...>]

On 26/09/2020 21:59, Stephen Williams wrote:
> I've made an 11.0 release, and the release source files are here:
> 
> <ftp://ftp.icarus.com/pub/eda/verilog/v11/>
> 
> Try it out, and let's see how it goes. Feedback in this mailing list,
> especially with packaging issues.
> 
I tested a clean checkout and build of the v11-branch. The version is 
reported as "11.0". Previous releases would report something like "10.3 
(stable)". The lack of a space after the version number caused the 
vpi/check_version test to segfault. I've fixed that.

[Iverilog-devel] Icarus Verilog Release 11.0

[Stephen W. <st...@ic...>]

I've made an 11.0 release, and the release source files are here:

<ftp://ftp.icarus.com/pub/eda/verilog/v11/>

Try it out, and let's see how it goes. Feedback in this mailing list,
especially with packaging issues.

-- 
Steve Williams                "The woods are lovely, dark and deep.
st...@ic...              But I have promises to keep,
http://www.icarus.com         and lines to code before I sleep,
http://www.picturel.com       And lines to code before I sleep."

Re: [Iverilog-devel] Version 11 for Icarus Verilog starting this weekend

[Cary R. <cy...@ya...>]

 Correct, lots more I would like to have done, but work and a broken machine intervened and what's there should be functional.
Cary

    On Thursday, September 24, 2020, 11:06:37 AM PDT, Stephen Williams <st...@ic...> wrote:  
 
 Cary? I think you're on record with no objections.

On Thu, Sep 24, 2020 at 10:22 AM Martin Whitaker
<ic...@ma...> wrote:
>
> No objection from me.
>
> On 24/09/2020 16:16, Stephen Williams wrote:
> > Thinking of starting the process of making the release this weekend,
> > September 26th/27th. Any objections?
>
>
> _______________________________________________
> Iverilog-devel mailing list
> Ive...@li...
> https://lists.sourceforge.net/lists/listinfo/iverilog-devel



-- 
Steve Williams                "The woods are lovely, dark and deep.
st...@ic...              But I have promises to keep,
http://www.icarus.com         and lines to code before I sleep,
http://www.picturel.com       And lines to code before I sleep."


_______________________________________________
Iverilog-devel mailing list
Ive...@li...
https://lists.sourceforge.net/lists/listinfo/iverilog-devel
  

Re: [Iverilog-devel] Version 11 for Icarus Verilog starting this weekend

[Stephen W. <st...@ic...>]

Cary? I think you're on record with no objections.

On Thu, Sep 24, 2020 at 10:22 AM Martin Whitaker
<ic...@ma...> wrote:
>
> No objection from me.
>
> On 24/09/2020 16:16, Stephen Williams wrote:
> > Thinking of starting the process of making the release this weekend,
> > September 26th/27th. Any objections?
>
>
> _______________________________________________
> Iverilog-devel mailing list
> Ive...@li...
> https://lists.sourceforge.net/lists/listinfo/iverilog-devel



-- 
Steve Williams                "The woods are lovely, dark and deep.
st...@ic...              But I have promises to keep,
http://www.icarus.com         and lines to code before I sleep,
http://www.picturel.com       And lines to code before I sleep."

Re: [Iverilog-devel] Version 11 for Icarus Verilog starting this weekend

[Martin W. <ic...@ma...>]

No objection from me.

On 24/09/2020 16:16, Stephen Williams wrote:
> Thinking of starting the process of making the release this weekend,
> September 26th/27th. Any objections?

[Iverilog-devel] Version 11 for Icarus Verilog starting this weekend

[Stephen W. <st...@ic...>]

Thinking of starting the process of making the release this weekend,
September 26th/27th. Any objections?


-- 
Steve Williams                "The woods are lovely, dark and deep.
st...@ic...              But I have promises to keep,
http://www.icarus.com         and lines to code before I sleep,
http://www.picturel.com       And lines to code before I sleep."