You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Chuck Rolke (JIRA)" <ji...@apache.org> on 2011/02/03 23:32:29 UTC
[jira] Created: (QPID-3038) Size_t demotion warnings on Windows x64
builds
Size_t demotion warnings on Windows x64 builds
----------------------------------------------
Key: QPID-3038
URL: https://issues.apache.org/jira/browse/QPID-3038
Project: Qpid
Issue Type: Improvement
Components: C++ Broker, C++ Client, C++ Clustering
Affects Versions: 0.8
Environment: C++ build for x64 windows platform
Reporter: Chuck Rolke
Priority: Minor
Scattered throughout the C++ source code are headers and source modules that treat size_t as int32_t, uint32_t, int, ULONG, and so on. Since the warnings are in .H files they are repeated dozens of times in any given build. I don't see any of the same warnings on a 64-bit linux build. Are they suppressed? Is this anything to worry about? None of the instances I've seen has any real problem until a buffer or I/O size gets up to around 2GB so they don't seem that bad.
59>C:\Hudson\jobs\...\qpid\cpp\src\qpid/sys/windows/AsynchIoResult.h(166) : warning C4267: '=' : conversion from 'size_t' to 'ULONG', possible loss of data
59>C:\Hudson\jobs\...\qpid\cpp\src\qpid/broker/Exchange.h(148) : warning C4267: 'return' : conversion from 'size_t' to 'uint32_t', possible loss of data
59>C:\Hudson\jobs\...\qpid\cpp\src\qpid/broker/Exchange.h(152) : warning C4267: 'return' : conversion from 'size_t' to 'uint32_t', possible loss of data
59>C:\Hudson\jobs\...\qpid\cpp\src\qpid/framing/ResizableBuffer.h(39) : warning C4267: 'argument' : conversion from 'size_t' to 'uint32_t', possible loss of data
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org
[jira] Closed: (QPID-3038) Size_t demotion warnings on Windows x64
builds
Posted by "Gordon Sim (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/QPID-3038?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gordon Sim closed QPID-3038.
----------------------------
Resolution: Duplicate
Duplicate of QPID-2574
> Size_t demotion warnings on Windows x64 builds
> ----------------------------------------------
>
> Key: QPID-3038
> URL: https://issues.apache.org/jira/browse/QPID-3038
> Project: Qpid
> Issue Type: Improvement
> Components: C++ Broker, C++ Client, C++ Clustering
> Affects Versions: 0.8
> Environment: C++ build for x64 windows platform
> Reporter: Chuck Rolke
> Priority: Minor
>
> Scattered throughout the C++ source code are headers and source modules that treat size_t as int32_t, uint32_t, int, ULONG, and so on. Since the warnings are in .H files they are repeated dozens of times in any given build. I don't see any of the same warnings on a 64-bit linux build. Are they suppressed? Is this anything to worry about? None of the instances I've seen has any real problem until a buffer or I/O size gets up to around 2GB so they don't seem that bad.
> 59>C:\Hudson\jobs\...\qpid\cpp\src\qpid/sys/windows/AsynchIoResult.h(166) : warning C4267: '=' : conversion from 'size_t' to 'ULONG', possible loss of data
> 59>C:\Hudson\jobs\...\qpid\cpp\src\qpid/broker/Exchange.h(148) : warning C4267: 'return' : conversion from 'size_t' to 'uint32_t', possible loss of data
> 59>C:\Hudson\jobs\...\qpid\cpp\src\qpid/broker/Exchange.h(152) : warning C4267: 'return' : conversion from 'size_t' to 'uint32_t', possible loss of data
> 59>C:\Hudson\jobs\...\qpid\cpp\src\qpid/framing/ResizableBuffer.h(39) : warning C4267: 'argument' : conversion from 'size_t' to 'uint32_t', possible loss of data
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org