attachment set

Fri, 22 Jun 2012 21:28:46 GMT

attachment → format_test3.cpp.patch

component changed; owner set

Fri, 22 Jun 2012 21:30:09 GMT

owner set to Samuel Krempp
component None → format

owner, status changed

James E. King, III — Sat, 14 Oct 2017 12:49:05 GMT

owner changed from Samuel Krempp to James E. King, III
status new → assigned

status changed; resolution set

James E. King, III — Sat, 14 Oct 2017 12:49:23 GMT

status assigned → closed
resolution → wontfix

I'm going to assume this is still an issue, given that in LP64 mode a long is 8 bytes. Here's the problem I have with the code and the patch:

The format value is "x" which means integer.
The value being inserted is -100 without decorations, so it should be treated as an integer.

Neither of these are long, which leads me to believe the submitted patch is a band-aid and not fixing the root cause. Furthermore, the boost project does not have a sunpro regression test in the matrix (http://www.boost.org/development/tests/develop/developer/format.html). I don't have an environment to debug this in either.

Further, the example you put into your description appears non-conformant to the standard. The value -1 is an integer, not a long integer. Even with stlsoft, _STLSOFT_SIZEOF_INT is always 4 even if _LP64 mode is on. (see: stlsoft-1.9.124 headers, include/stlsort/internal/cccap/sunpro.h). Given the failure occurs when stlsoft is added, my guess is stlsoft is to blame.

I am going to close this issue as wontfix since the environment is not conforming to the language rules.

Boost C++ Libraries: Ticket #7019: In libs/format/test/format_test3.cpp, 64-bit Solaris stlport4 iostream produces different result for stlport4

attachment set

component changed; owner set

owner, status changed

status changed; resolution set