Hello Dave Dave Korn wrote:
That's odd. I'm guessing 'sparse' is some kind of source code parser? For whatever reason, the version of ieeefp.h in my cygwin installation doesn't include any related #warning or #error. Is sparse somehow generating that itself?
Yeah, the Linux guys use it in order to track down bugs. AFAICT, Sparse doesn't change the header files, so I'm a little puzzled by the fact that your version doesn't include the #error directive at the end.
Not all built-in #defines come from the specs. For the canonical list of built-in definitions, which vary slightly between C and C++, use: gcc -x c -E -dM - < /dev/null g++ -x c++ -E -dM - < /dev/null
Thanks. That revealed many #define's that I wasn't aware of. I will try and apply them and see how far that gets me.
-- Best Regards Kovarththanan Rajaratnam -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
