You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafficserver.apache.org by "James Peach (JIRA)" <ji...@apache.org> on 2012/07/28 17:52:34 UTC
[jira] [Created] (TS-1385) generic atomic operations API
James Peach created TS-1385:
-------------------------------
Summary: generic atomic operations API
Key: TS-1385
URL: https://issues.apache.org/jira/browse/TS-1385
Project: Traffic Server
Issue Type: Improvement
Components: Core
Affects Versions: 3.3.0
Reporter: James Peach
Assignee: James Peach
Priority: Minor
Rather than ink_atomic_increment32(), ink_atomic_increment64() and friends we should just have a generic ink_atomic_increment() that works for all the types we do atomic ops on. This is more reliable is cases where the size of a type varies between different systems (eg. time_t).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (TS-1385) generic atomic operations API
Posted by "James Peach (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TS-1385?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13424369#comment-13424369 ]
James Peach commented on TS-1385:
---------------------------------
I'm using templates for gcc-comparible compilers because the type matching is stricter. SunPro gets an overloaded function because it's a smaller change and I can't test it.
> generic atomic operations API
> -----------------------------
>
> Key: TS-1385
> URL: https://issues.apache.org/jira/browse/TS-1385
> Project: Traffic Server
> Issue Type: Improvement
> Components: Core
> Affects Versions: 3.3.0
> Reporter: James Peach
> Assignee: James Peach
> Priority: Minor
>
> Rather than ink_atomic_increment32(), ink_atomic_increment64() and friends we should just have a generic ink_atomic_increment() that works for all the types we do atomic ops on. This is more reliable is cases where the size of a type varies between different systems (eg. time_t).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (TS-1385) generic atomic operations API
Posted by "James Peach (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TS-1385?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
James Peach resolved TS-1385.
-----------------------------
Resolution: Fixed
Fix Version/s: 3.3.0
76aa879db6d7d418486afba8804893d2133a5811 TS-1385: generic atomic operations API
> generic atomic operations API
> -----------------------------
>
> Key: TS-1385
> URL: https://issues.apache.org/jira/browse/TS-1385
> Project: Traffic Server
> Issue Type: Improvement
> Components: Core
> Affects Versions: 3.3.0
> Reporter: James Peach
> Assignee: James Peach
> Priority: Minor
> Fix For: 3.3.0
>
>
> Rather than ink_atomic_increment32(), ink_atomic_increment64() and friends we should just have a generic ink_atomic_increment() that works for all the types we do atomic ops on. This is more reliable is cases where the size of a type varies between different systems (eg. time_t).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira