Menu
▾
▴
iverilog-devel
|
From: Stephen W. <st...@ic...> - 2015-04-08 20:38:30
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I know this has been discussed before, but I want to bring it up again. I think we are due for a new release. I've been noting that a huge portion of users are finding that their needs are met by recent snapshots that are not otherwise handled by the 0.9 release. We've been spending some amount of our support time just telling people that "it's been fixed" in the master branch. But there are many users out there who get their Icarus Verilog fix from package managers, and so are using the 0.9 release. These people are not particularly motivated to build from source, and after all they shouldn't need to. Our making a release is our way to say that this is what we recommend. Since we've been recommending git master for a while now, maybe it is time to make a release. Also, name change. Rather then go to 0.10.x, let's simple call it version 10. Somewhere along the line, Icarus Verilog became production ready while we weren't looking. I think the leading zero is no longer informative. - -- Steve Williams "The woods are lovely, dark and deep. steve at icarus.com 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." -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlUlkb0ACgkQrPt1Sc2b3ike8ACgtA+gOWgr5ZOntDvQyqcblsEe DcAAn1r+o1mkZVP0o4ceRA7Y24OlDVbK =/jyw -----END PGP SIGNATURE----- |
|
From: <dp...@sw...> - 2015-04-08 22:56:03
|
Hello, I am very new to Icarus so I am not in a position to say something in this thread. But just to mentioned that I needed "Constant user functions" support so I had to compile the trunk. Best Regards Dimitar -----Original Message----- From: Stephen Williams Sent: Wednesday, April 8, 2015 23:38 To: Discussions concerning Icarus Verilog development Subject: [Iverilog-devel] Thinking of Icarus Verilog 10 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I know this has been discussed before, but I want to bring it up again. I think we are due for a new release. I've been noting that a huge portion of users are finding that their needs are met by recent snapshots that are not otherwise handled by the 0.9 release. We've been spending some amount of our support time just telling people that "it's been fixed" in the master branch. But there are many users out there who get their Icarus Verilog fix from package managers, and so are using the 0.9 release. These people are not particularly motivated to build from source, and after all they shouldn't need to. Our making a release is our way to say that this is what we recommend. Since we've been recommending git master for a while now, maybe it is time to make a release. Also, name change. Rather then go to 0.10.x, let's simple call it version 10. Somewhere along the line, Icarus Verilog became production ready while we weren't looking. I think the leading zero is no longer informative. - -- Steve Williams "The woods are lovely, dark and deep. steve at icarus.com 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." -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlUlkb0ACgkQrPt1Sc2b3ike8ACgtA+gOWgr5ZOntDvQyqcblsEe DcAAn1r+o1mkZVP0o4ceRA7Y24OlDVbK =/jyw -----END PGP SIGNATURE----- ------------------------------------------------------------------------------ BPM Camp - Free Virtual Workshop May 6th at 10am PDT/1PM EDT Develop your own process in accordance with the BPMN 2 standard Learn Process modeling best practices with Bonita BPM through live exercises http://www.bonitasoft.com/be-part-of-it/events/bpm-camp-virtual- event?utm_ source=Sourceforge_BPM_Camp_5_6_15&utm_medium=email&utm_campaign=VA_SF _______________________________________________ Iverilog-devel mailing list Ive...@li... https://lists.sourceforge.net/lists/listinfo/iverilog-devel |
|
From: Martin W. <mai...@ma...> - 2015-04-08 22:59:34
|
Stephen Williams wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > > I know this has been discussed before, but I want to bring it up > again. I think we are due for a new release. > > I've been noting that a huge portion of users are finding that > their needs are met by recent snapshots that are not otherwise > handled by the 0.9 release. We've been spending some amount of > our support time just telling people that "it's been fixed" in > the master branch. > > But there are many users out there who get their Icarus Verilog > fix from package managers, and so are using the 0.9 release. These > people are not particularly motivated to build from source, and > after all they shouldn't need to. Our making a release is our > way to say that this is what we recommend. > > Since we've been recommending git master for a while now, maybe > it is time to make a release. > You know this will get my vote! Development is a huge advance over v0.9 - time to get it in the hands of all our users. Martin |
|
From: XINGZHI W. <xin...@ho...> - 2015-04-09 00:05:09
|
Hi Stephen, It has been a while since I use Icarus simulator. Could you please share any update about UVM and system verilog support? ThanksXingzhi > Date: Wed, 8 Apr 2015 23:59:26 +0100 > From: mai...@ma... > To: ive...@li... > Subject: Re: [Iverilog-devel] Thinking of Icarus Verilog 10 > > Stephen Williams wrote: > > -----BEGIN PGP SIGNED MESSAGE----- > > Hash: SHA1 > > > > > > I know this has been discussed before, but I want to bring it up > > again. I think we are due for a new release. > > > > I've been noting that a huge portion of users are finding that > > their needs are met by recent snapshots that are not otherwise > > handled by the 0.9 release. We've been spending some amount of > > our support time just telling people that "it's been fixed" in > > the master branch. > > > > But there are many users out there who get their Icarus Verilog > > fix from package managers, and so are using the 0.9 release. These > > people are not particularly motivated to build from source, and > > after all they shouldn't need to. Our making a release is our > > way to say that this is what we recommend. > > > > Since we've been recommending git master for a while now, maybe > > it is time to make a release. > > > You know this will get my vote! Development is a huge advance over v0.9 - time > to get it in the hands of all our users. > > Martin > > ------------------------------------------------------------------------------ > BPM Camp - Free Virtual Workshop May 6th at 10am PDT/1PM EDT > Develop your own process in accordance with the BPMN 2 standard > Learn Process modeling best practices with Bonita BPM through live exercises > http://www.bonitasoft.com/be-part-of-it/events/bpm-camp-virtual- event?utm_ > source=Sourceforge_BPM_Camp_5_6_15&utm_medium=email&utm_campaign=VA_SF > _______________________________________________ > Iverilog-devel mailing list > Ive...@li... > https://lists.sourceforge.net/lists/listinfo/iverilog-devel |
|
From: <ni...@ly...> - 2015-04-15 13:45:24
|
Stephen Williams <st...@ic...> writes: > Also, name change. Rather then go to 0.10.x, let's simple call > it version 10. Somewhere along the line, Icarus Verilog became > production ready while we weren't looking. Cool! But why not simply "1.0"? Regards, /Niels -- Niels Möller. PGP-encrypted email is preferred. Keyid C0B98E26. Internet email is subject to wholesale government surveillance. |
|
From: Stephen W. <st...@ic...> - 2015-04-15 14:26:52
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 04/15/2015 06:45 AM, Niels Möller wrote: > Stephen Williams <st...@ic...> writes: > >> Also, name change. Rather then go to 0.10.x, let's simple call it >> version 10. Somewhere along the line, Icarus Verilog became >> production ready while we weren't looking. > > Cool! But why not simply "1.0"? The previous version is 0.9.x, it's been informally called the "point 9" release, it just feels like I'm shifting the decimal point over one. It's purely aesthetic. - -- Steve Williams "The woods are lovely, dark and deep. steve at icarus.com 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." -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlUudSEACgkQrPt1Sc2b3imeygCfSS+HzcFWOAhrSyQ7/nb3I+x3 pLMAoJnh6jmQC4gtt3dbS6FfbzTjtspQ =PwdJ -----END PGP SIGNATURE----- |
|
From: Stephen W. <st...@ic...> - 2015-04-17 23:22:10
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I've gotten generally positive feedback from this idea, so I'm going to set a deadline for objections. If I don't hear any objects by the evening of Saturday, 25 April 2015, I will feel free to start wrapping up an Icarus Verilog release anytime from the 26th on. This will involve locally testing the package build, then making a branch and making an actual draft release. Maybe a week after the draft release, I'll probably make the Version 10 release (10.1) and we can start promoting the new release to distribution packagers. Sound like a plan? On 04/08/2015 01:38 PM, Stephen Williams wrote: > > I know this has been discussed before, but I want to bring it up > again. I think we are due for a new release. > > I've been noting that a huge portion of users are finding that > their needs are met by recent snapshots that are not otherwise > handled by the 0.9 release. We've been spending some amount of our > support time just telling people that "it's been fixed" in the > master branch. > > But there are many users out there who get their Icarus Verilog fix > from package managers, and so are using the 0.9 release. These > people are not particularly motivated to build from source, and > after all they shouldn't need to. Our making a release is our way > to say that this is what we recommend. > > Since we've been recommending git master for a while now, maybe it > is time to make a release. > > Also, name change. Rather then go to 0.10.x, let's simple call it > version 10. Somewhere along the line, Icarus Verilog became > production ready while we weren't looking. I think the leading zero > is no longer informative. - -- Steve Williams "The woods are lovely, dark and deep. steve at icarus.com 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." -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlUxlZgACgkQrPt1Sc2b3ilgygCfZwaCxK+dLv6fQ74DROSxF5iP Sg4An1z0kq9UnKOmoZnazfwNTiY2SdAh =uzVD -----END PGP SIGNATURE----- |
|
From: Stephen W. <st...@ic...> - 2015-04-25 01:11:54
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 04/08/2015 01:38 PM, Stephen Williams wrote: > I know this has been discussed before, but I want to bring it up > again. I think we are due for a new release. I threatened to start making the release this weekend, but some issues have come up, so instead I will make a snapshot. This will be a dry run for making the release, but otherwise will have no other consequences. (It's also been a long time since the last snapshot.) I've delayed the proposed release date to May 10. That too is a working date, not cast in stone. - -- Steve Williams "The woods are lovely, dark and deep. steve at icarus.com 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." -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlU66c8ACgkQrPt1Sc2b3ilnFgCgycqwqpX3pxiPZQsN+yN2ZqtT H+8AoKytk13nKttIxfrd7ODLpbOayyot =ATJx -----END PGP SIGNATURE----- |
|
From: Stephen W. <st...@ic...> - 2015-08-11 17:52:27
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I've been talked out of making a version 10 release several times now, but this time I think I'm going to make an executive decision. We need a version 10 release. It's getting desperate. The 0.9.7 release is very old, and too many of the bug reports we received are from the 0.9 release and have been already fixed in the devel branch. I have some free time this coming weekend (August 15,16) so I think I will make the branch and make a draft release then. I'm not taking requests to hold off anymore, we'll instead discuss how to fit your pet project into the development path. On 04/24/2015 06:11 PM, Stephen Williams wrote: > On 04/08/2015 01:38 PM, Stephen Williams wrote: >> I know this has been discussed before, but I want to bring it up >> again. I think we are due for a new release. > > I threatened to start making the release this weekend, but some > issues have come up, so instead I will make a snapshot. This will > be a dry run for making the release, but otherwise will have no > other consequences. (It's also been a long time since the last > snapshot.) > > I've delayed the proposed release date to May 10. That too is a > working date, not cast in stone. - -- Steve Williams "The woods are lovely, dark and deep. steve at icarus.com 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." -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlXKNk8ACgkQrPt1Sc2b3imENQCg2WdnkD77PgGXJvoN3jJMm6pd xRAAnj3jhnIGTTJGvnX9ohSxiB9GbODi =arUf -----END PGP SIGNATURE----- |
|
From: Martin W. <mai...@ma...> - 2015-08-11 22:36:17
|
Stephen Williams wrote: > I've been talked out of making a version 10 release several > times now, but this time I think I'm going to make an executive > decision. > > We need a version 10 release. It's getting desperate. The 0.9.7 > release is very old, and too many of the bug reports we received > are from the 0.9 release and have been already fixed in the devel > branch. > +1 from me (as usual!). I've just checked that everything still compiles and runs as expected under Windows/MinGW. Just one thing needs attention - the latest vhdlpp patches have introduce some shift/reduce errors: bison --verbose -t -d -o parse.cc ../../source/vhdlpp/parse.y ../../source/vhdlpp/parse.y: warning: 90 shift/reduce conflicts [-Wconflicts-sr] ../../source/vhdlpp/parse.y: warning: 30 reduce/reduce conflicts [-Wconflicts-rr] Martin |
|
From: Larry D. <ldo...@re...> - 2015-08-12 01:29:55
|
Steve - On Tue, Aug 11, 2015 at 11:23:08PM +0100, Martin Whitaker wrote: > Stephen Williams wrote: > > We need a version 10 release. It's getting desperate. > Just one thing needs attention - the latest vhdlpp patches have introduce some > shift/reduce errors: I also see parse.cc:7759:18: warning: missing initializer for member ‘vlltype::text’ [-Wmissing-field-initializers] And the string "elabortae_rootscope_tasks does not understand " in elab_scope.cc should have elabortae changed to elaborate. - Larry |
Thanks for helping keep SourceForge clean.
X