Return-Path: X-Original-To: apmail-httpd-dev-archive@www.apache.org Delivered-To: apmail-httpd-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 1820C91C1 for ; Sun, 18 Dec 2011 17:17:23 +0000 (UTC) Received: (qmail 10485 invoked by uid 500); 18 Dec 2011 17:17:22 -0000 Delivered-To: apmail-httpd-dev-archive@httpd.apache.org Received: (qmail 10407 invoked by uid 500); 18 Dec 2011 17:17:22 -0000 Mailing-List: contact dev-help@httpd.apache.org; run by ezmlm Precedence: bulk Reply-To: dev@httpd.apache.org list-help: list-unsubscribe: List-Post: List-Id: Delivered-To: mailing list dev@httpd.apache.org Received: (qmail 10399 invoked by uid 99); 18 Dec 2011 17:17:22 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 18 Dec 2011 17:17:22 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=5.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: local policy) Received: from [188.40.99.202] (HELO eru.sfritsch.de) (188.40.99.202) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 18 Dec 2011 17:17:15 +0000 Received: from [10.1.1.6] (helo=k.localnet) by eru.sfritsch.de with esmtp (Exim 4.72) (envelope-from ) id 1RcKM2-0003EO-V8 for dev@httpd.apache.org; Sun, 18 Dec 2011 18:16:55 +0100 From: Stefan Fritsch To: dev@httpd.apache.org Subject: Re: Win64 2.3.16 :: build warnings Date: Sun, 18 Dec 2011 18:16:54 +0100 User-Agent: KMail/1.13.7 (Linux/3.1.0-1-amd64; KDE/4.6.5; x86_64; ; ) References: <27924EBFEF834107A9279E94F545B292@Father> In-Reply-To: <27924EBFEF834107A9279E94F545B292@Father> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-15" Content-Transfer-Encoding: 7bit Message-Id: <201112181816.54428.sf@sfritsch.de> 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?