celix-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bjoern Petri (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CELIX-233) Replace booleans as sync primitives
Date Sat, 16 May 2015 09:02:59 GMT

    [ https://issues.apache.org/jira/browse/CELIX-233?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14546651#comment-14546651
] 

Bjoern Petri commented on CELIX-233:
------------------------------------


It would be interesting to get that clarified. I created this issue based on the information
I got from this page:
https://www.securecoding.cert.org/confluence/display/c/CON02-C.+Do+not+use+volatile+as+a+synchronization+primitive



> Replace booleans as sync primitives
> -----------------------------------
>
>                 Key: CELIX-233
>                 URL: https://issues.apache.org/jira/browse/CELIX-233
>             Project: Celix
>          Issue Type: Bug
>            Reporter: Bjoern Petri
>            Assignee: Bjoern Petri
>
> In a lot of cases we use boolean variables (e.g. bool running) to determine whether a
critical section can be executed. Usually those variables are not declared volatile, so the
they may be cached in registers. Before the value in the register is written to memory, another
thread might be scheduled to run, resulting in that thread reading stale data.
> But even when declaring a variable as volatile (although the volatile qualifier guarantees
that the reads and writes will happen in the exact order specified in the source code), the
compiler may generate code which reorders a volatile read or write with non-volatile reads
or writes, thus limiting its usefulness as an interthread flag or mutex.
> That's why it should be preferable to use e.g. a mutex as sync primitive



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message