[
https://issues.apache.org/jira/browse/TS-1829?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13634575#comment-13634575
]
James Peach commented on TS-1829:
---------------------------------
{code}
diff --git a/lib/records/RecUtils.cc b/lib/records/RecUtils.cc
index d04fce7..b51af3f 100644
--- a/lib/records/RecUtils.cc
+++ b/lib/records/RecUtils.cc
@@ -76,7 +76,7 @@ RecDataSetMax(RecDataT type, RecData * data)
#endif
case RECD_INT:
case RECD_COUNTER:
- data->rec_int = 0x7fffffffffffffff;
+ data->rec_int = 0x7fffffffffffffffll;
break;
#if defined(STAT_PROCESSOR)
case RECD_CONST:
{code}
Maybe this?
> Hardcoded numeric values exceed capacity of 'long' data type on 32-bit
> ----------------------------------------------------------------------
>
> Key: TS-1829
> URL: https://issues.apache.org/jira/browse/TS-1829
> Project: Traffic Server
> Issue Type: Bug
> Components: Stats
> Reporter: Nick Kew
> Fix For: 3.3.3
>
>
> Compile failure:
> cc1plus: warnings being treated as errors
> RecUtils.cc:79: error: integer constant is too large for ‘long’ type
> RecUtils.cc:101: error: integer constant is too large for ‘long’ type
> make[2]: *** [libreclocal_a-RecUtils.o] Error 1
> Either the datatype needs changing to be explicitly 64-bit, or the values
> 0x7fffffffffffffff and 0x8000000000000000 need switching to a
> platform-sensitive LONG_MAX construct.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
