Trusster Forums » Recent Posts

Trusster Forums » Recent Posts http://forums.trusster.com/ Trusster Forums » Recent Posts en Fri, 30 Jul 2010 14:51:39 +0000 germanattanasio on "Teal build error Fedora" http://forums.trusster.com/topic/teal-build-error-fedora#post-42 Sun, 18 Jul 2010 20:30:17 +0000 germanattanasio 42@http://forums.trusster.com/ In order to fix "should have been declared inside ‘teal’" on Ubuntu. I had to: 0. Checkout the code from subversion repositories. 1. Install gcc-4.1 and g++-4.1 from Synaptic. 2. change <code>SYS_ARCH_CC</code> to use gcc-4.1. <a href="http://www.trusster.com/truss/howto-configure-svn-for-read-only-access/" rel="nofollow">http://www.trusster.com/truss/howto-configure-svn-for-read-only-access/</a> Mike Mintz on "Teal build error Fedora" http://forums.trusster.com/topic/teal-build-error-fedora#post-41 Mon, 28 Jun 2010 14:52:37 +0000 Mike Mintz 41@http://forums.trusster.com/ Hi, There are actually two patches: *** teal_reg.h.new 2010-06-28 14:47:39.000000000 -0400 --- teal_reg.h 2006-05-18 08:34:00.000000000 -0400 *************** EVEN IF ADVISED OF THE POSSIBILITY OF SU *** 110,117 **** char to_int (uint32 b) const; //extract one bit (WARNING: Drops X/Z, see operator(uint32)) //logic ! friend four_state ::teal::triple_equal (const reg& lhs, const reg& rhs); ! friend bool ::teal::operator== (const reg& lhs, const reg& rhs); friend four_state operator< (const reg& lhs, const reg& rhs); //Should be bool? friend four_state reduce_xor (const reg&); --- 110,117 ---- char to_int (uint32 b) const; //extract one bit (WARNING: Drops X/Z, see operator(uint32)) //logic ! friend four_state triple_equal (const reg& lhs, const reg& rhs); ! friend bool operator== (const reg& lhs, const reg& rhs); friend four_state operator< (const reg& lhs, const reg& rhs); //Should be bool? friend four_state reduce_xor (const reg&); *************** EVEN IF ADVISED OF THE POSSIBILITY OF SU *** 284,290 **** friend vout& operator<< (vout&, const vreg&); }; vout& operator<< (vout&, const vreg&); - - reg::four_state triple_equal (const reg& lhs, const reg& rhs); - bool operator== (const reg& lhs, const reg& rhs); - reg::four_state operator< (const reg& lhs, const reg& rhs); //Should be bool? --- 284,286 ---- -and - *** teal_vreg.cpp.new 2010-06-28 14:45:41.000000000 -0400 --- teal_vreg.cpp 2010-06-28 14:45:28.000000000 -0400 *************** void teal::vreg::connect_ () { *** 143,149 **** #if defined (vpi_2_0) if (! handle_) { ! local_log << teal_error << "Unable to get handle for \"" << path_and_name_ << "\" size:" << (int)path_and_name_.size () << endm; vpi_control (vpiFinish); } --- 143,149 ---- #if defined (vpi_2_0) if (! handle_) { ! local_log << teal_error << "Unable to get handle for \"" << path_and_name_ << "\" size:" << path_and_name_.size () << endm; vpi_control (vpiFinish); } shakthimaan on "Teal build error Fedora" http://forums.trusster.com/topic/teal-build-error-fedora#post-40 Mon, 28 Jun 2010 11:25:57 +0000 shakthimaan 40@http://forums.trusster.com/ Can you please let me know line 309 in which file? In teal_reg.cpp line 309 contains: //now clean off any whole word parts, I am zero above assignment if (i < word_length_) { //work to do for (; i < word_length_; i++) { // std::cout << "teal::reg::operator=() clearing word =" < teal_acc_vecval_[i].aval = 0; teal_acc_vecval_[i].bval = 0; } } In teal_reg.h the last line is only 286. If you could create a patch, with the required changes it will be easy to follow than replying with snippets. This is also the reason why I like mailing lists for easier discussions and follow-up. I am using teal_1_40b.tar.gz. Thanks! Mike Mintz on "Teal build error Fedora" http://forums.trusster.com/topic/teal-build-error-fedora#post-39 Thu, 24 Jun 2010 16:06:38 +0000 Mike Mintz 39@http://forums.trusster.com/ Hi, Humm, can I believe some revs of gcc want the declaration also in the teal scope. Can you add the following starting at line 309? reg::four_state triple_equal (const reg& lhs, const reg& rhs); bool operator== (const reg& lhs, const reg& rhs); reg::four_state operator< (const reg& lhs, const reg& rhs); Sorry about this. Take Care, mike shakthimaan on "Teal build error Fedora" http://forums.trusster.com/topic/teal-build-error-fedora#post-38 Thu, 24 Jun 2010 12:29:15 +0000 shakthimaan 38@http://forums.trusster.com/ I have the following in teal_reg.h and I still get the same error: //logic friend four_state ::teal::triple_equal (const reg& lhs, const reg& rhs); friend bool ::teal::operator== (const reg& lhs, const reg& rhs); friend four_state ::teal::operator< (const reg& lhs, const reg& rhs); //Should be bool? friend four_state reduce_xor (const reg&); ./teal_reg.cpp:391: error: ‘bool teal::operator==(const teal::reg&, const teal::reg&)’ should have been declared inside ‘teal’ ./teal_reg.cpp:398: error: ‘teal::reg::four_state teal::triple_equal(const teal::reg&, const teal::reg&)’ should have been declared inside ‘teal’ ./teal_reg.cpp:428: error: ‘teal::reg::four_state teal::operator<(const teal::reg&, const teal::reg&)’ should have been declared inside ‘teal’ admin on "Teal build error Fedora" http://forums.trusster.com/topic/teal-build-error-fedora#post-37 Thu, 24 Jun 2010 11:47:39 +0000 admin 37@http://forums.trusster.com/ There's an article on the site describing how to get read-only access to the SVN repository. It can be found at <a href="http://www.trusster.com/truss/howto-configure-svn-for-read-only-access/" rel="nofollow">http://www.trusster.com/truss/howto-configure-svn-for-read-only-access/</a> . If you have trouble, let me or Mike know. admin on "Mailing list" http://forums.trusster.com/topic/mailing-list#post-36 Thu, 24 Jun 2010 11:47:12 +0000 admin 36@http://forums.trusster.com/ There's an article on the site describing how to get read-only access to the SVN repository. It can be found at <a href="http://www.trusster.com/truss/howto-configure-svn-for-read-only-access/" rel="nofollow">http://www.trusster.com/truss/howto-configure-svn-for-read-only-access/</a> . If you have trouble, let me or Mike know. Mike Mintz on "Mailing list" http://forums.trusster.com/topic/mailing-list#post-35 Wed, 23 Jun 2010 09:52:43 +0000 Mike Mintz 35@http://forums.trusster.com/ Hi, Great idea ! I will ask my IT person to do that. Can you ping me privately mike >< trusster >< com ? That way, we can send you the svn key. Take care, Mike Mike Mintz on "Teal build error Fedora" http://forums.trusster.com/topic/teal-build-error-fedora#post-34 Wed, 23 Jun 2010 09:51:08 +0000 Mike Mintz 34@http://forums.trusster.com/ Hi, start at line 117. Alternatively you could search for triple_equal Take Care, Mike shakthimaan on "Mailing list" http://forums.trusster.com/topic/mailing-list#post-33 Tue, 22 Jun 2010 06:44:47 +0000 shakthimaan 33@http://forums.trusster.com/ I am trying to package Teal for Fedora. 1. Can you please create a mailing list for discussions, and submission of patches? 2. If you could also remove the login requirement, and provide an RSS feed for source code, it will be very helpful to keep track of new releases! Thanks! shakthimaan on "Teal build error Fedora" http://forums.trusster.com/topic/teal-build-error-fedora#post-32 Tue, 22 Jun 2010 06:26:16 +0000 shakthimaan 32@http://forums.trusster.com/ I am now using teal_1_40b with gcc 4.4.4 on Fedora 13. Where should I include the following? Anyway, to fix it, add the global scope resolution operator on the function names: <pre><code>friend four_state ::teal::triple_equal (const reg& lhs, const reg& rhs); friend bool ::teal::operator== (const reg& lhs, const reg& rhs); friend four_state ::teal::operator< (const reg& lhs, const reg& rhs); //Should be bool?</code></pre> Mike Mintz on "Active HDL (Windows)" http://forums.trusster.com/topic/active-hdl-windows#post-31 Tue, 04 May 2010 08:33:20 +0000 Mike Mintz 31@http://forums.trusster.com/ Hi Rolf, Thanks for trying Teal/Truss and working on these run time issues. Yeah the synch and mutex code is just ugly. I have good contacts at Aldec and will get them to try teal on windows. I know they use teal on Linux in their regression suite. If you can get me a stack dump of the crash I will take a look. As for truss, can you get me the error from the compiler. I agree that I made a bad assumption that pthread_t was an integral type. You can see in the run_loop class (just below the thread class in truss_thread.h) that I use a bool to track the state. As for the redundant code in stop(), the idea it to protect if you call stop() again. pthread does not handle a second cancel or join very well. Aldec is a proper simulator. It seem to me you are following the code quite well ! I have been coding c++ for 20 years now and would not consider myself an expert. I will get back to you when I hear from aldec. Take Care, mike shimrod on "Active HDL (Windows)" http://forums.trusster.com/topic/active-hdl-windows#post-30 Tue, 04 May 2010 05:10:34 +0000 shimrod 30@http://forums.trusster.com/ Hi Im trying to get teal (1.40b) and Truss to work with Active HDL 8.2 under windows XP, with pthreads.2 and the mingw gcc compiler that comes with the simulator. I have managed to compile teal (PLI 1) and some of the tests passes. However the mutex_test crashes the simulator. I tried to play with the number of threads and up to 4 works. When I change the no of iterations to 1 I can create many (250) threads. So it seems to me that something with the mutex fails. Regarding Truss, I can't compile since the different implementation of pthread_t. Truss seems to rely on the id being 0 after thread cancelled? Also this seems redundant since teal::stop_Thread is calling both ptrhead_cancel and pthread_join. Anyone who has some ideas? Or should I give up and move to linux and a proper simulator? Im not an C++ (or C) expert and the code is quite complex to follow. Thanks and best regards Rolf Mike Mintz on "Teal build error Fedora" http://forums.trusster.com/topic/teal-build-error-fedora#post-29 Wed, 28 Apr 2010 10:24:17 +0000 Mike Mintz 29@http://forums.trusster.com/ Hi Dave, I think it's this line: local_log << teal_error << "Unable to get handle for \"" << path_and_name_ << "\" size:" << (unsigned)path_and_name_.size () << endm; If so that would be my stupid hack to get 32 bit working with .size(). Just remove the (unsigned) cast. I am happy that you are finding the book useful. Take Care, mike -- The details -- The issue is that I did not do a signed uint64 operator<< for teal_vout. You can change the size_t operator<<() to be the correct form: virtual vout& operator<< (long long int x) {return operator<< ( (unsigned long long) x);} Sorry about that. daveW on "Teal build error Fedora" http://forums.trusster.com/topic/teal-build-error-fedora#post-28 Tue, 27 Apr 2010 20:30:46 +0000 daveW 28@http://forums.trusster.com/ Robert I hacked on this some the other night and boiled it down to line 150 (or within a few lines) in 'teal_vreg.cpp'. Seems to be a problem with the call to 'path_and_name_.size ()'. When commenting this out, I can successfully build the library. Hey, I'm enjoying your book - HW verification with C++. You guys are trailblazers. Dave daveW on "Teal build error Fedora" http://forums.trusster.com/topic/teal-build-error-fedora#post-27 Mon, 26 Apr 2010 13:46:41 +0000 daveW 27@http://forums.trusster.com/ Robert OK - that should work. Again the error appears to be related to one file - 'teal_vreg.cpp'. Remove this file in the 'makefile' and it builds successfully. Thank you for your quick response. Dave Robert Ekendahl on "Teal build error Fedora" http://forums.trusster.com/topic/teal-build-error-fedora#post-26 Mon, 26 Apr 2010 12:03:35 +0000 Robert Ekendahl 26@http://forums.trusster.com/ Dave, Mike's on vacation and I must confess I don't have teal for c++ running currently on any of my computers. I'm sure Mike will be able to help you as soon as he gets back later this week. /Robert daveW on "Teal build error Fedora" http://forums.trusster.com/topic/teal-build-error-fedora#post-25 Mon, 26 Apr 2010 11:54:23 +0000 daveW 25@http://forums.trusster.com/ All I'm having one file fail on a Teal build on SUSE 10.2 with gcc 4.1.2. The build will work if I remove 'teal_vreg.cpp'. Here is some of the error message...using 'make -d'. It is ugly.. and I'm seeking some help. :char_traits<char>, _Alloc = std::allocator<char>]()’ ./teal_vout.h:131: note: candidates are: virtual teal::vout&teal::vout::operator<<(char) ./teal_vout.h:132: note: virtual teal::vout& teal::vout::operator<<(int) ./teal_vout.h:133: note: virtual teal::vout& teal::vout::operator<<(unsigned int) ./teal_vout.h:134: note: virtual teal::vout& teal::vout::operator<<(long int) ./teal_vout.h:135: note: virtual teal::vout& teal::vout::operator<<(long long unsigned int) ./teal_vout.h:136: note: virtual teal::vout& teal::vout::operator<<(const std::string&) <near match> ./teal_vout.h:137: note: virtual teal::vout& teal::vout::operator<<(double) ./teal_vout.h:159: note: teal::vout& teal::vout::operator<<(teal::vout& (*)(teal::vout&)) <near match> ./teal_reg.h:191: note: teal::vout& teal::operator<<(teal::vout&, teal::reg::four_state) <near match> ./teal_reg.h:188: note: teal::vout& teal::operator<<(teal::vout&, const teal::reg&) Reaping losing child 0x0064c140 PID 5951 make: *** [teal_vreg.o] Error 1 Removing child 0x0064c140 PID 5951 from chain. This is using a recent 1_40b Teal archive. Scope resolution ("teal:: ") looks to be in place. cheers, Dave flyfishr64 on "Can't get back to main site from forum" http://forums.trusster.com/topic/cant-get-back-to-main-site-from-forum#post-24 Wed, 17 Mar 2010 16:09:38 +0000 flyfishr64 24@http://forums.trusster.com/ I second the motion! admin on "Can't get back to main site from forum" http://forums.trusster.com/topic/cant-get-back-to-main-site-from-forum#post-23 Wed, 17 Mar 2010 15:30:32 +0000 admin 23@http://forums.trusster.com/ Hey guys, can you add a link back to the main site from the forums? Mike Mintz on "error while compiling teal in icarus verilog" http://forums.trusster.com/topic/error-while-compiling-teal-in-icarus-verilog#post-22 Wed, 17 Mar 2010 15:06:44 +0000 Mike Mintz 22@http://forums.trusster.com/ Hi amitbaran, Sorry for the long delay. Our notification system is broken. Can I see what command you used? It looks like the make in teal did not complete. Take Care, mike Mike Mintz on "Crash: Ubuntu/Icarus/GCC ?" http://forums.trusster.com/topic/crash-ubuntuicarusgcc#post-21 Wed, 17 Mar 2010 15:00:37 +0000 Mike Mintz 21@http://forums.trusster.com/ Hi Steven, Can you try running under gdb ? Another possibility is to try without the $verification_top() call. Finally, try dropping to the simpler teal tests. Sorry I could not be more useful. Take Care, Mike Mike Mintz on "Teal build error Fedora" http://forums.trusster.com/topic/teal-build-error-fedora#post-20 Wed, 17 Mar 2010 14:56:45 +0000 Mike Mintz 20@http://forums.trusster.com/ Hi, Sorry for the delay in a response. Our notification system is broken. I have seen this error "should have been declared inside ‘teal’". It has to do with the newer gcc. I actually think its a bug, because its not overleading the scope correctly. Anyway, to fix it, add the global scope resolution operator on the function names: friend four_state ::teal::triple_equal (const reg& lhs, const reg& rhs); friend bool ::teal::operator== (const reg& lhs, const reg& rhs); friend four_state ::teal::operator< (const reg& lhs, const reg& rhs); //Should be bool? Take care, Mike Mike Mintz on "error while compiling teal" http://forums.trusster.com/topic/error-while-compiling-teal#post-19 Wed, 17 Mar 2010 14:48:04 +0000 Mike Mintz 19@http://forums.trusster.com/ Hi, Sorry for the delay in responding. Since teal_memory.cpp:95 and 364 are just a log lines, you can comment them out. Feel free to e-mail me directly at mike <> trusster <> com Again, I apologize for the delay. take Care, mike Mike Mintz on "Building shared libary" http://forums.trusster.com/topic/building-shared-libary#post-18 Wed, 17 Mar 2010 14:42:39 +0000 Mike Mintz 18@http://forums.trusster.com/ Hi digimike10, So sorry for the delay. The "automatic ping" system seems to be broken. In order to respond, I need more of the log file. You command seems fine. Take Care, Mike mike <> trusster <> com Mike Mintz on "error occurs when running Teal sv in Questasim6.5c" http://forums.trusster.com/topic/error-occurs-when-running-teal-sv-in-questasim65c#post-17 Thu, 18 Feb 2010 11:34:22 +0000 Mike Mintz 17@http://forums.trusster.com/ Hi Desperado, (Are you the same Desperado as on the Verification Guild?) Sorry for the delay in responding. Our normal notification system failed. SV certainly has the *required* features to allow verification to succeed. It's just not good at encouraging good programming practices and has lots of "sharp corners" in its language definition. By far, the primary wart on the SV language is the difficulty in separation of interface versus implementation. This is a staple of good languages since the 1970s. You can separate *most* symbols (data, methods, classes), but it requires significant work on the coders part. There are tons of glitches in this process like the poor definition of a forwarded class type, how prototypes can vary between declaration and definition, and the initialization of statics. A second major flaw is that SV is derived from Verilog. This brings a host of issues and encumbrances, but the main one is that Verilog is designed to build real physical entities. The ways that that warps a language design are numerous. Just look at compilation versus elaboration and what are the scope resolution rules for a.b . Now C++ is weaker in some regards, such as threading, 4/8 state computations and connection to the DUT, but these can be overcome with relative ease (i.e. Teal). A third major flaw is that it does not integrate well with c and c++. These are the two primary languages of software. Yes, I know about DPI and PLI, they are quite weak for real model integration. Here's a partial list of lesser flaws. I am just rattling them off in no particular order. C++ has the std namespace and the template library. This alone is a major piece of good work and provides a good base for both novice and expert programmers. Many books have been written on the Template Library and much though has gone into those templates/algorithms. I know and have used all of SVs container classes, but they are a weak shadow of the template library. Packages versus namespaces: There are two major faults. The first is that when you end a package, all the methods and classes must be fully defined. This breaks the separation of interface and implementation. Add to that the fact that the parser and language definition are weak and you end up with files like teal_vout_pre and teal_vout_post. Another fault is that the package cannot be added to in another file. This may seem silly, but I do not want everything associated with a specific functional area to be in one file. How would users add they own derivations and have them look like there are "inside" the package ? A small nit is the fact that a function cannot take time. Either that or methods should be allowed to return a value. C++ has automatic construction and destruction. This is of great use for managing entry/exit tasks, such a mutex sentries, scratch RAM allocation, and resource reservation. It is invaluable in these situations within a function with many return points. Now I realize SV has pointer management, but (1) this can be added to C++ easily using smart pointers, (2) is often not really an issue and (3) causes great confusion as to when to new and when to copy. The fact that the language does not support a copy constructor leaves us to write error prone and clumsy code (with down casts). C++ is known by millions of programmers and hundreds of books are available. SV has maybe 20 thousand programmers and a handful of books. The inheritance model if SV is very weak. It does not support protected or private inheritance or multiple inheritance. It's model of function resolution follows the pointer type which is just wrong. Parametrization versus templating: There is only a superficial comparison and SV has not real facility for meta-programming (templating). Good templating is critical to the design of good container classes and generic algorithms. We do a lot of similar things in verification, it's real hard to express this commonality. Now I realize this is used in perhaps only 1% of your code (with the major exception of container classes and algorithms) parameters in SV versus constants in c++: Just looking at the ability one has to specify constants for reusable code, SV is weak. There is still discussion as to whether there can be global parameters. The initialization of parameters is very weak compared to c++. Finally the type checking in parameters is weak. bind versus operator overloading: As far as I know, no vendor has implemented bin for the purpose of overloading mathematical operators. Sorry this post was so long; I just got going. To me SV is like playing a concert on a toy piano. Sure you can try, but your range, sound and general talent is limited to, well playing like a child. desperadoo on "error occurs when running Teal sv in Questasim6.5c" http://forums.trusster.com/topic/error-occurs-when-running-teal-sv-in-questasim65c#post-16 Mon, 08 Feb 2010 06:45:51 +0000 desperadoo 16@http://forums.trusster.com/ Hi All, Robert Ekendahl Wrote: ""This is why I think our C++ solutions is far superior. You get a mature language with tons of more features then SV and you don't have to go through all of these hoops to make it work across simulators."" Hi Robert, can you name a few features as you say, c++ has rich features than SV,,,,?? As SV language supports all what available to verify an RTL design, what extra do you require to verify the RTL design!!! Can you suggest some few major feature which you C++ solutions provide over the SV !! so that would be helpful to know about the same!! Thanks, Desperado --> Keen on Teal/Truss solutions digimike10 on "Building shared libary" http://forums.trusster.com/topic/building-shared-libary#post-15 Tue, 26 Jan 2010 02:02:02 +0000 digimike10 15@http://forums.trusster.com/ Error messages when using truss "./truss --simulator NCSIM --test alu_test": gcc:/home/michael/truss/src/truss_verification_top.o: No such file or directory gcc:/home/michael/truss/src/truss_watchdog.o: No such file or directory gcc:/home/michael/russ/examples/block_uart/verification/tests/alu_test.o: No such file or directory ... Could you please advice? -M jagan on "error while compiling teal" http://forums.trusster.com/topic/error-while-compiling-teal#post-14 Thu, 07 Jan 2010 14:41:20 +0000 jagan 14@http://forums.trusster.com/ Hi Mike I got the same error and and now I get the following error when compiling after making the change you suggested ((uint32)aval_start_ to (size_t)aval_start_) in teal_memory.cpp In file included from ./teal.h:137, from ./teal_memory.cpp:32: ./teal_reg.h:95: warning: ‘typedef’ was ignored in this declaration ./teal_memory.cpp: In constructor ‘regular_memory_bank::regular_memory_bank(const std::string&)’: ./teal_memory.cpp:364: error: ambiguous overload for ‘operator<<’ in ‘((teal::vout*)((teal::vout*)((teal::vout*)((teal::vout*)((teal::vout*)((teal::vout*)teal::operator<< [with TP1 = const std::string&, TP2 = std::pair<int, int>](((teal::vout&)(&<unnamed>::local_log)), ((const teal::vmanip<const std::string&, std::pair<int, int> >&)((const teal::vmanip<const std::string&, std::pair<int, int> >*)(& teal::mark_start(((const std::string&)(& std::basic_string<char, std::char_traits<char>, std::allocator<char> >(((const char*)"./teal_memory.cpp"), ((const std::allocator<char>&)((const std::allocator<char>*)(& std::allocator<char>())))))), std::pair<int, int>(((const int&)((const int*)(&2055))), ((const int&)((const int*)(&363))))))))))->teal::vout::operator<<(((const std::string&)(& std::basic_string<char, std::char_traits<char>, std::allocator<char> >(((const char*)"Memory ctor: bytes_per_group_ "), ((const std::allocator<char>&)((const std::allocator<char>*)(& std::allocator<char>()))))))))->teal::vout::operator<<(((regular_memory_bank*)this)->regular_memory_bank::bytes_per_group_))->teal::vout::operator<<(((const std::string&)(& std::basic_string<char, std::char_traits<char>, std::allocator<char> >(((const char*)" bit_length_ : "), ((const std::allocator<char>&)((const std::allocator<char>*)(& std::allocator<char>()))))))))->teal::vout::operator<<(((regular_memory_bank*)this)->regular_memory_bank::bit_length_))->teal::vout::operator<<(teal::hex))->teal::vout::operator<<(((const std::string&)(& std::basic_string<char, std::char_traits<char>, std::allocator<char> >(((const char*)" aval_start: "), ((const std::allocator<char>&)((const std::allocator<char>*)(& std::allocator<char>()))))))) << (size_t)((regular_memory_bank*)this)->regular_memory_bank::aval_start_’ ./teal_vout.h:131: note: candidates are: virtual teal::vout& teal::vout::operator<<(char) ./teal_vout.h:132: note: virtual teal::vout& teal::vout::operator<<(int) What can I do to get over this error. Also, do you have a different version/download for 64bit machines.? Thanks moogyd on "Teal build error Fedora" http://forums.trusster.com/topic/teal-build-error-fedora#post-13 Tue, 05 Jan 2010 11:52:38 +0000 moogyd 13@http://forums.trusster.com/ Hi, I'm not a C++ expert, but this problem can be fixed by editing the Makefiles to add the --friend_injection option gcc. Let me know if you manage to get everything running under Fodora - I am at a deadend under Ubuntu :-() Steven shakthimaan on "Teal build error Fedora" http://forums.trusster.com/topic/teal-build-error-fedora#post-12 Wed, 30 Dec 2009 02:46:34 +0000 shakthimaan 12@http://forums.trusster.com/ I am trying to build Teal (teal_1_40b.tar.gz) on Fedora 12 using gcc 4.4.2: $ export SIMULATOR_HOME=/usr $ ARCH=Linux make SIM=ivl gcc -c -fPIC ./teal_reg.cpp -o ./teal_reg.o -Wall -Dvpi_2_0 -DSIM=ivl -Divl -I. -I/usr/include -I/usr/pli_incs -I/usr/pli/interface In file included from ./teal.h:136, from ./teal_reg.cpp:32: ./teal_vout.h:149: warning: ‘typedef’ was ignored in this declaration In file included from ./teal.h:137, from ./teal_reg.cpp:32: ./teal_reg.h:95: warning: ‘typedef’ was ignored in this declaration ./teal_reg.cpp:391: error: ‘bool teal::operator==(const teal::reg&, const teal::reg&)’ should have been declared inside ‘teal’ ./teal_reg.cpp:398: error: ‘teal::reg::four_state teal::triple_equal(const teal::reg&, const teal::reg&)’ should have been declared inside ‘teal’ ./teal_reg.cpp:428: error: ‘teal::reg::four_state teal::operator<(const teal::reg&, const teal::reg&)’ should have been declared inside ‘teal’ make: *** [teal_reg.o] Error 1 Has anyone been able to successfully build Teal on *nix? Please let me know how to proceed. moogyd on "Crash: Ubuntu/Icarus/GCC ?" http://forums.trusster.com/topic/crash-ubuntuicarusgcc#post-11 Sat, 19 Dec 2009 12:10:31 +0000 moogyd 11@http://forums.trusster.com/ Hi, I am running on Ubuntu 8.04. I don't know where the problem is, but when I try to run the examples (e.g. alu_test), I get a "crash" Running Simulation resultfile /home/stevend/work/teal_truss/examples/alu/results/alu_test_1_results.log *** glibc detected *** vvp: free(): invalid pointer: 0x080e57f8 *** ======= Backtrace: ========= /lib/tls/i686/cmov/libc.so.6[0xb7d02a85] /lib/tls/i686/cmov/libc.so.6(cfree+0x90)[0xb7d064f0] /usr/lib/libstdc++.so.6(_ZdlPv+0x21)[0xb7bcbb11] /usr/lib/libstdc++.so.6(_ZNSs4_Rep10_M_destroyERKSaIcE+0x1d)[0xb7ba779d] /usr/lib/libstdc++.so.6(_ZNSsD1Ev+0x51)[0xb7ba9571] hdl/alu_test.ivl.so(_Z18teal_scan_plusargsRKSs+0x20f)[0xb7c6e4d1] hdl/alu_test.ivl.so(_ZN4teal10dictionary4findERKSs+0x25)[0xb7c6e5a3] hdl/alu_test.ivl.so(_ZN4teal10dictionary4findIjEET_RKSsS2_+0x2e)[0xb7c65d08] hdl/alu_test.ivl.so(_ZN4teal4voutC1ERKSs+0x53)[0xb7c60887] hdl/alu_test.ivl.so[0xb7c6c210] hdl/alu_test.ivl.so[0xb7c6c2a0] hdl/alu_test.ivl.so[0xb7c821e5] hdl/alu_test.ivl.so[0xb7c382e4] /lib/ld-linux.so.2[0xb7ef99d0] /lib/ld-linux.so.2[0xb7ef9b03] /lib/ld-linux.so.2[0xb7efd7b4] /lib/ld-linux.so.2[0xb7ef9606] /lib/ld-linux.so.2[0xb7efcf8e] /lib/tls/i686/cmov/libdl.so.2[0xb7ed1c19] /lib/ld-linux.so.2[0xb7ef9606] /lib/tls/i686/cmov/libdl.so.2[0xb7ed22bc] /lib/tls/i686/cmov/libdl.so.2(dlopen+0x41)[0xb7ed1b51] vvp(_Z16vpip_load_modulePKc+0xb7)[0x80793d7] vvp(main+0x490)[0x8057dd0] /lib/tls/i686/cmov/libc.so.6(__libc_start_main+0xe0)[0xb7cad450] vvp(__gxx_personality_v0+0x41d)[0x8057781] ======= Memory map: ======== 08048000-08099000 r-xp 00000000 08:01 1196961 /usr/local/bin/vvp 08099000-0809a000 rw-p 00051000 08:01 1196961 /usr/local/bin/vvp 0809a000-080f1000 rw-p 0809a000 00:00 0 [heap] b7900000-b7921000 rw-p b7900000 00:00 0 b7921000-b7a00000 ---p b7921000 00:00 0 b7afc000-b7b10000 r-xp 00000000 08:01 184662 /lib/tls/i686/cmov/libpthread-2.7.so b7b10000-b7b12000 rw-p 00013000 08:01 184662 /lib/tls/i686/cmov/libpthread-2.7.so b7b12000-b7b14000 rw-p b7b12000 00:00 0 b7b14000-b7bfc000 r-xp 00000000 08:01 752761 /usr/lib/libstdc++.so.6.0.9 b7bfc000-b7bff000 r--p 000e8000 08:01 752761 /usr/lib/libstdc++.so.6.0.9 b7bff000-b7c01000 rw-p 000eb000 08:01 752761 /usr/lib/libstdc++.so.6.0.9 b7c01000-b7c07000 rw-p b7c01000 00:00 0 b7c07000-b7c93000 r-xp 00000000 08:01 408811 /home/stevend/work/teal_truss/examples/alu/results/hdl/alu_test.ivl.so b7c93000-b7c96000 rw-p 0008c000 08:01 408811 /home/stevend/work/teal_truss/examples/alu/results/hdl/alu_test.ivl.so b7c96000-b7c97000 rw-p b7c96000 00:00 0 b7c97000-b7de0000 r-xp 00000000 08:01 184624 /lib/tls/i686/cmov/libc-2.7.so b7de0000-b7de1000 r--p 00149000 08:01 184624 /lib/tls/i686/cmov/libc-2.7.so b7de1000-b7de3000 rw-p 0014a000 08:01 184624 /lib/tls/i686/cmov/libc-2.7.so b7de3000-b7de6000 rw-p b7de3000 00:00 0 b7de6000-b7df0000 r-xp 00000000 08:01 184186 /lib/libgcc_s.so.1 b7df0000-b7df1000 rw-p 0000a000 08:01 184186 /lib/libgcc_s.so.1 b7df1000-b7e14000 r-xp 00000000 08:01 184636 /lib/tls/i686/cmov/libm-2.7.so b7e14000-b7e16000 rw-p 00023000 08:01 184636 /lib/tls/i686/cmov/libm-2.7.so b7e16000-b7e17000 rw-p b7e16000 00:00 0 b7e17000-b7ec7000 r-xp 00000000 08:01 752569 /usr/lib/libstdc++.so.5.0.7 b7ec7000-b7ecc000 rw-p 000af000 08:01 752569 /usr/lib/libstdc++.so.5.0.7 b7ecc000-b7ed1000 rw-p b7ecc000 00:00 0 b7ed1000-b7ed3000 r-xp 00000000 08:01 184631 /lib/tls/i686/cmov/libdl-2.7.so b7ed3000-b7ed5000 rw-p 00001000 08:01 184631 /lib/tls/i686/cmov/libdl-2.7.so b7ee9000-b7eeb000 rw-p b7ee9000 00:00 0 b7eeb000-b7eec000 r-xp b7eeb000 00:00 0 [vdso] b7eec000-b7f06000 r-xp 00000000 08:01 184320 /lib/ld-2.7.so b7f06000-b7f08000 rw-p 00019000 08:01 184320 /lib/ld-2.7.so bf889000-bf89e000 rw-p bffeb000 00:00 0 [stack] Aborted System call failed at ../truss/bin/truss line 461 main::truss_system('cd /home/stevend/work/teal_truss/examples/alu/results; vvp -m...') called at ../truss/bin/truss line 384 Other Information: gcc -v Using built-in specs. Target: i486-linux-gnu Configured with: ../src/configure -v --enable-languages=c,c++,fortran,objc,obj-c++,treelang --prefix=/usr --enable-shared --with-system-zlib --libexecdir=/usr/lib --without-included-gettext --enable-threads=posix --enable-nls --with-gxx-include-dir=/usr/include/c++/4.2 --program-suffix=-4.2 --enable-clocale=gnu --enable-libstdcxx-debug --enable-objc-gc --enable-mpfr --enable-targets=all --enable-checking=release --build=i486-linux-gnu --host=i486-linux-gnu --target=i486-linux-gnu Thread model: posix gcc version 4.2.4 (Ubuntu 4.2.4-1ubuntu4) VM:~/work/teal_truss/examples> iverilog -V Icarus Verilog version 0.8 ($Name: s20050617 $) I assume it's not directly a problem with Teal/Truss, but more to do with my environment (I have also tried with gcc-3.3 with the same results) Any ideas? Thanks, Steven amitbaran on "error while compiling teal in icarus verilog" http://forums.trusster.com/topic/error-while-compiling-teal-in-icarus-verilog#post-10 Mon, 16 Nov 2009 14:31:16 +0000 amitbaran 10@http://forums.trusster.com/ Hi, I used icarus verilog to test the teal library but I got the following error, can you please help me to solve this. I am using the instructions written on the teal user guide. In file included from ../teal.h:137, from ./reg_test.cpp:37: ../teal_vout.h:149: warning: ‘typedef’ was ignored in this declaration In file included from ../teal.h:138, from ./reg_test.cpp:37: ../teal_reg.h:95: warning: ‘typedef’ was ignored in this declaration make: *** No rule to make target <code>../libteal.ivl.a', needed by</code>reg_test.ivl.so'. Stop. Robert Ekendahl on "error occurs when running Teal sv in Questasim6.5c" http://forums.trusster.com/topic/error-occurs-when-running-teal-sv-in-questasim65c#post-9 Thu, 08 Oct 2009 08:42:06 +0000 Robert Ekendahl 9@http://forums.trusster.com/ Cool, I'm glad that it's working. We also found that our code was working up to 6.4 with MTI and this is an issue we have been going back and forth with them on. They are probably the closest to the LRM, but the LRM is bad and many standard coding practices cannot be used if you follow the LRM. VCS and others choose to ignore the LRM. Not sure that is good either. This is why I think our C++ solutions is far superior. You get a mature language with tons of more features then SV and you don't have to go through all of these hoops to make it work across simulators. Our C++ solution also avoids the pitfall that SystemC and it's templating mess. That all said, we have an exiting solution in the works where we merge Teal/Truss with SystemC. Hiding most of the ugliness of SystemC and allowing verification to be more efficient while still connecting in other SystemC IP blocks. I hope Mike will be ready to show this soon. hanibian on "error occurs when running Teal sv in Questasim6.5c" http://forums.trusster.com/topic/error-occurs-when-running-teal-sv-in-questasim65c#post-8 Wed, 07 Oct 2009 22:31:02 +0000 hanibian 8@http://forums.trusster.com/ Hi Mike and Robert, Thanks for your both replies. I can proceed the simulation after removing "= 0", although there are still some warnings. Yes, sv is still under developing and not all the features are supported by EDA vendors, even some features have been interpretated differently by different vendors, or by the same vendor in its different S/W versions. Anyway I believed this is not an error of Teal, since I ran it on VCS-2008.x and there's no warnings or errors. Thanks again for your efforts. Best regards, Hanibian