From: Stephen W. <st...@ic...> - 2008-01-11 22:20:06
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I find myself waiting on simulations today so am looking into making a devel snapshot. Are there any outstanding patches that people really want to see in this snapshot? I'm in the process of going through the Patches tracker to apply those already submitted patches. - -- 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 v1.4.2 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iD8DBQFHh+uYrPt1Sc2b3ikRAr1iAJ9oMsuUg5UTASFgIIgsZK+VpTJDTQCeLpGs urRXCfSwNunw0yGIc+ynvyA= =kY2y -----END PGP SIGNATURE----- |
From: Larry D. <ldo...@re...> - 2008-01-11 22:31:36
|
Steve - On Fri, Jan 11, 2008 at 02:20:08PM -0800, Stephen Williams wrote: > Are there any outstanding patches that people really > want to see in this snapshot? I'm in the process of going through the > Patches tracker to apply those already submitted patches. Nope, everything's fine here. I just verified that the build-in-another-directory step works even without write access to the source directory (a test that pcb flunks). It Would Be Nice if you could get rid of vvp/vpi_priv.cc:121: warning: deprecated conversion from string constant to 'char*' I never researched how info->code gets used. - Larry |
From: Cary R. <cy...@ya...> - 2008-01-12 00:39:48
|
--- Stephen Williams <st...@ic...> wrote: > I find myself waiting on simulations today so am looking into making > a devel snapshot. Are there any outstanding patches that people really > want to see in this snapshot? I'm in the process of going through the > Patches tracker to apply those already submitted patches. At this point I am GTG. I just submitted my last active patch. I wanted to get the VA math code into the next snapshot, but since I had not planned to package it until the weekend it is not ready for release today. Cary ____________________________________________________________________________________ Be a better friend, newshound, and know-it-all with Yahoo! Mobile. Try it now. http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ |
From: Stephen W. <st...@ic...> - 2008-01-12 00:51:41
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Cary R. wrote: > --- Stephen Williams <st...@ic...> wrote: > >> I find myself waiting on simulations today so am looking into making >> a devel snapshot. Are there any outstanding patches that people really >> want to see in this snapshot? I'm in the process of going through the >> Patches tracker to apply those already submitted patches. > > At this point I am GTG. I just submitted my last active patch. I wanted to > get the VA math code into the next snapshot, but since I had not planned > to package it until the weekend it is not ready for release today. In the interest of stability, I've decided to actually skip the patch that you just submitted to the Patches tracker. I've pushed the tag that I used, and I have release notes in the ftp directory. Note that the list of changes since 20070812 is so huge that I got bored writing the release notes and started using generalizations:-) <ftp://ftp.icarus.com/pub/eda/verilog/snapshots/verilog-20080111.txt> Comments before I post an announcement? - -- 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 v1.4.2 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iD8DBQFHiA8hrPt1Sc2b3ikRAi+9AJ9sl27axUfBbHRxD59JBDIuoQog1wCgiw79 Mz2eJRztdGrRbSkMsMzXGAk= =LhA2 -----END PGP SIGNATURE----- |
From: Cary R. <cy...@ya...> - 2008-01-12 01:21:14
|
--- Stephen Williams <st...@ic...> wrote: > In the interest of stability, I've decided to actually skip the > patch that you just submitted to the Patches tracker. Understand. I'm fairly sure everything is correct, but a little seasoning never hurts either. > I've pushed > the tag that I used, and I have release notes in the ftp directory. > Note that the list of changes since 20070812 is so huge that I > got bored writing the release notes and started using generalizations:-) That's what you get for waiting five month between snapshots ;-). > Comments before I post an announcement? Correct file and line information is currently only generated and passed for system functions and only two functions ($bitstoreal and $realtobits) have been actually updated to use this new information. Other objects return dummy values ("N/A", 0). This allows programs that use vpiFile and vpiLineNo to be compiled, but it will be a while before everything meaningful in Icarus fully supports this. Hopefully most of the system functions will be updated by the next snapshot. Cary ____________________________________________________________________________________ Looking for last minute shopping deals? Find them fast with Yahoo! Search. http://tools.search.yahoo.com/newsearch/category.php?category=shopping |
From: Larry D. <ldo...@re...> - 2008-01-13 04:53:15
|
On Fri, Jan 11, 2008 at 02:20:08PM -0800, Stephen Williams wrote: > I find myself waiting on simulations today so am looking into making > a devel snapshot. Are there any outstanding patches that people really > want to see in this snapshot? I'm in the process of going through the > Patches tracker to apply those already submitted patches. Not-so-minor issue I just ran into installing on a fresh computer (I'm rebuilding my laptop -- Gutsy Gibbon, not that it matters). The build rules for eval_bool.o don't include a proper include directory to search for _pli_types.h. gcc -DHAVE_CVS_IDENT=1 -I. -I../../verilog/tgt-vvp/.. -DHAVE_CONFIG_H -fPIC -Wall -g -O2 -MD -c ../../verilog/tgt-vvp/eval_bool.c -o eval_bool.o ../../verilog/tgt-vvp/eval_bool.c:23:57: error: _pli_types.h: No such file or directory ../../verilog/tgt-vvp/eval_bool.c: In function `draw_number_bool64': ../../verilog/tgt-vvp/eval_bool.c:67: error: expected ')' before 'PLI_UINT64_FMT' ../../verilog/tgt-vvp/eval_bool.c:67: warning: too few arguments for format make[1]: *** [eval_bool.o] Error 1 I think I never hit this before because I always had a previous valid install, so it finds _pli_types.h from that .. but I'm not sure. It looks like adding -I.. will do. <tappety-typ> Yup, that works, I checked. This problem is new (as of commit 21730ab228e5812f8b09b4f9b50843f343b99321), we just added the include so we could print a uint64_t properly (standards-compliantly). - Larry |
From: Stephen W. <st...@ic...> - 2008-01-14 17:54:35
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hmm, this could be slightly tricky. Larry Doolittle wrote: > On Fri, Jan 11, 2008 at 02:20:08PM -0800, Stephen Williams wrote: >> I find myself waiting on simulations today so am looking into making >> a devel snapshot. Are there any outstanding patches that people really >> want to see in this snapshot? I'm in the process of going through the >> Patches tracker to apply those already submitted patches. > > Not-so-minor issue I just ran into installing on a fresh computer > (I'm rebuilding my laptop -- Gutsy Gibbon, not that it matters). > > The build rules for eval_bool.o don't include a proper include > directory to search for _pli_types.h. > > gcc -DHAVE_CVS_IDENT=1 -I. -I../../verilog/tgt-vvp/.. -DHAVE_CONFIG_H -fPIC -Wall -g -O2 -MD -c ../../verilog/tgt-vvp/eval_bool.c -o eval_bool.o > ../../verilog/tgt-vvp/eval_bool.c:23:57: error: _pli_types.h: No such file or directory > ../../verilog/tgt-vvp/eval_bool.c: In function `draw_number_bool64': > ../../verilog/tgt-vvp/eval_bool.c:67: error: expected ')' before 'PLI_UINT64_FMT' > ../../verilog/tgt-vvp/eval_bool.c:67: warning: too few arguments for format > make[1]: *** [eval_bool.o] Error 1 > > I think I never hit this before because I always had a previous valid > install, so it finds _pli_types.h from that .. but I'm not sure. > It looks like adding -I.. will do. <tappety-typ> Yup, that works, I checked. The general idea is that code generator source should not ever peek into other Icarus Verilog source. They are supposed to be separable. Also, although _pli_types.h is sorta public, I don't think eval_bool.c should include it at all. It turns out that eval_bool.c is using PLI_UINT64_FMT to match a uint64_t; it should be using the STDMACROS from <inttypes.h>. I've pushed a change into git. You'll need to rerun autoconf.sh to make the configure scripts, and reconfigure for the change to take effect. This should only be a problem on systems where the inttypes.h header file doesn't exist. - -- 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 v1.4.2 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iD8DBQFHi6HRrPt1Sc2b3ikRAnPVAJ9BM6QUkxk+jGPXBGrhGhH1uDpRLACfeOtV QE42kGb+Ya9ffBqGm55AeAY= =Ekau -----END PGP SIGNATURE----- |