-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 08/23/2011 05:52 AM, Richard Hipp wrote: > (1) Compilers sometimes make mistakes. So it is important that you test > your object code - not just your source code. That means running your test > cases using exactly the same *.o files that you use for delivery. "Fly what > you test and test what you fly."
I would recommend also compiling and running the test suite using PCC (it is becoming the standard compiler on BSDs), CLANG (increasingly pervasive) and the Intel compiler (known for strong optimisations, excellent VTune performance analysis tool). http://en.wikipedia.org/wiki/Portable_C_Compiler http://software.intel.com/en-us/articles/intel-parallel-studio-xe/ > (2) I need to come up with a second, independent method of verifying branch > test coverage in SQLite. It looks like you need both a compiler that generates the necessary information in the debug tables and a profiling tool that knows how to read that. I can only find gcc+gcov doing that, although the Intel tools may do so as well. It seems like you should be able to get statement test coverage using almost any compiler and gcov or callgrind, which is better than nothing but not as good as branch coverage. Roger -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk5TMSwACgkQmOOfHg372QQkEgCaAkX4Nl8ezZwgP6eDinWh1NIz ORQAoN3TN2+WMc3QumnXxDcsEp+eDOo7 =dEiZ -----END PGP SIGNATURE----- _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
