On Thu, Jun 5, 2014 at 2:15 PM, David Mertens <[email protected]> wrote:
> Hello jiang, > > However, this will only impose a speed penalty on the compiler, it will > not make it any faster. If you decide to try to implement it, you must > write benchmarks showing how much slower tcc will run for some important > compilation targets. Take a large project, such as Awk, and see how much > slower it takes to compile with these warnings implemented. See how much > more memory it will consume. If the numbers involve a negligible change, > you might get buy-in. (Note: negligible is in the eye of the beholder. A 1% > slow-down may be too much.) > Also, tools already exist for this issue (for example see cppcheck on github). These tools do a excellent job of detecting uninitialized variables, plus many other checks. Using the tool in conjunction with tcc is likely a better approach. -- Charles
_______________________________________________ Tinycc-devel mailing list [email protected] https://lists.nongnu.org/mailman/listinfo/tinycc-devel
