Mario1159/verilator
1
0
Fork 0
forked from github/verilator
Code Pull Requests Releases 1 Activity

Speed display, bug373.

Browse Source
This commit is contained in:
Wilson Snyder 2012-11-02 17:54:14 -04:00
parent 7ef37d6e17
commit 0e921b5dff
3 changed files with 10 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
Changes
View File

@ -9,7 +9,7 @@ indicates the contributor was also the author of the fix; Thanks!
**** Fix large shift error on large shift constants. [David Welch]
**** Fix $display mangling on GCC 4.7, msg927. [R Diez]
**** Fix $display mangling on GCC 4.7 and speed up, msg927, bug373. [R Diez]
**** Fix missing var access functions when no DPI, bug572. [Amir Gonnen]

2
include/verilated.cpp
View File

@ -308,7 +308,7 @@ void _vl_vsformat(string& output, const char* formatp, va_list ap) {
const char *ep = pos;
while (ep[0] && ep[0]!='%') ep++;
if (ep != pos) {
output += string(pos, ep-pos);
output.append(pos, ep-pos);
pos += ep-pos-1;
}
} else { // Format character

9
internals.pod
View File

@ -371,6 +371,13 @@ the documentation in:
test_regress/t/driver.pl --help
It is important to add tests for failures as well as success (for example to
check that an error message is correctly triggered).
Tests that fail should by convenition have the suffix C<_bad> in their name,
and include C<fails =E<gt> 1> in either their C<compile> or C<execute> step as
appropriate.
Developers will also want to configure with two extra flags:
=over 4
@ -382,7 +389,7 @@ ensure no sloppy code gets added, however it can be painful when it comes
to testing, since third party code used in the tests (e.g. SystemC) may not
be warning free.
=item --enable-long-tests
=item --enable-longtests
In addition to the standard C, SystemC and SystemPerl tests also run the
tests in the C<test_vcs>, C<test_verilated> and C<test_regress> directories