You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Vinod Kone (JIRA)" <ji...@apache.org> on 2015/06/25 22:20:06 UTC
[jira] [Resolved] (MESOS-2925) Invalid usage of ATOMIC_FLAG_INIT in
member initialization
[ https://issues.apache.org/jira/browse/MESOS-2925?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Vinod Kone resolved MESOS-2925.
-------------------------------
Resolution: Fixed
Fix Version/s: 0.23.0
commit f62530487198ce170e664e47902ddd5ab2b90d6f
Author: Paul Brett <pa...@twopensource.com>
Date: Thu Jun 25 13:19:09 2015 -0700
Fixed usage of ATOMIC_FLAG_INIT.
Review: https://reviews.apache.org/r/35841
> Invalid usage of ATOMIC_FLAG_INIT in member initialization
> ----------------------------------------------------------
>
> Key: MESOS-2925
> URL: https://issues.apache.org/jira/browse/MESOS-2925
> Project: Mesos
> Issue Type: Bug
> Components: libprocess
> Affects Versions: 0.23.0
> Reporter: Paul Brett
> Assignee: Paul Brett
> Fix For: 0.23.0
>
>
> The C++ specification states:
> The macro ATOMIC_FLAG_INIT shall be defined in such a way that it can be used to initialize an object of type atomic_flag to the clear state. The macro can be used in the form: "atomic_flag guard = ATOMIC_FLAG_INIT; "It is unspecified whether the macro can be used in other initialization contexts."
> Clang catches this (although reports it erroneously as a braced scaled init issue) and refuses to compile libprocess.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)