Hi Steffen, On Saturday 17 December 2011, Steffen wrote: > Here the Win64 warnings attached. > > Quite a lot, 442.
Most of these are conversions between various integer types. I think the majority of these are in fact correct code. It would be quite a lot of worth to fix these and I am not sure that it would be worth the effort. I would recommend to simply disable that warning for now. The same is true for various signed/unsigned mismatch warnings. BTW, some warnings lack line numbers and can't be checked ATM. After filtering these out, the following remain: > Warning 111 warning C4715: 'ap_expr_str_exec_re' : not all > control paths return a value e:\vc9\win64\httpd-2.3.16- beta\server\util_expr_eval.c 925 This seems to imply that the compiler does not know that ap_log_assert() does not return. Is there some equivalent of __attribute__(noreturn) for VC? > Warning 161 warning C4133: 'function' : incompatible types - > from 'timeval *' to 'l_timeval *' E:\VC9\Win64\httpd-2.3.16- > beta\modules\ldap\util_ldap.c 502 > Warning 162 warning C4133: 'function' : incompatible types - > from 'timeval *' to 'l_timeval *' E:\VC9\Win64\httpd-2.3.16- > beta\modules\ldap\util_ldap.c 937 > Warning 163 warning C4133: 'function' : incompatible types - > from 'timeval *' to 'l_timeval *' E:\VC9\Win64\httpd-2.3.16- > beta\modules\ldap\util_ldap.c 1688 > Warning 164 warning C4133: 'function' : incompatible types - > from 'timeval *' to 'l_timeval *' E:\VC9\Win64\httpd-2.3.16- > beta\modules\ldap\util_ldap.c 1946 I don't know what l_timeval is. But if Windows ldap uses something different than timeval, maybe there should be some #ifdef magic to deal with that. > Warning 165 warning LNK4013: image size 0x12000 exceeds > specified maximum 0x10000 mod_ldap This sounds like it could be a problem. Can some Windows dev take a look?
