I have built SphinxBase and PocketSphinx (5pre-alpha) on Windows 7 32-bit, with Visual Studio 2015.
I get many warnings in many files. Most of them are due to narrowing conversion, or signed/unsigned conversion, like:
warning C4244: '=': conversion from 'float32' to 'int32', possible loss of data
warning C4018: '>=': signed/unsigned mismatch
There is one instance of warning C4267, in the file fe_interface.c:
warning C4267: '+=': conversion from 'size_t' to 'int16', possible loss of data
There are also four instances of warning C4090: 'function': different 'const' qualifiers.
I guess that the official binaries were compiled without warnings. If so, with which compiler/tools they were compiled? Do you think that compiling with VS2010 or gcc will solve the problem?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I have built SphinxBase and PocketSphinx (5pre-alpha) on Windows 7 32-bit, with Visual Studio 2015.
I get many warnings in many files. Most of them are due to narrowing conversion, or signed/unsigned conversion, like:
warning C4244: '=': conversion from 'float32' to 'int32', possible loss of data
warning C4018: '>=': signed/unsigned mismatch
There is one instance of warning C4267, in the file fe_interface.c:
warning C4267: '+=': conversion from 'size_t' to 'int16', possible loss of data
There are also four instances of warning C4090: 'function': different 'const' qualifiers.
I have attached the logs.
Last edit: Oren G. 2018-01-06
Thank you for report, it would be nice for someone to fix all this, but that will probably happen in the next century.
I guess that the official binaries were compiled without warnings. If so, with which compiler/tools they were compiled? Do you think that compiling with VS2010 or gcc will solve the problem?
No, warnings always were there, I just ignored them always.