Talk:Barrier (computer science)

message: prevent the compiler from reordering other operations over the barrier statement during optimization passes.
WTF does "over the barrier" mean? Examples are in order.  —Preceding unsigned comment added by 97.116.107.166 (talk) 05:38, 7 January 2010 (UTC)
thread_title:  Clarifications needed 

message: The included pseudocode examples have numerous correctness issues (ex. data races) and the notation quality is also lacking (type and/or initial values are not clear). Examples of how to use the barrier primitive(s) may also help.  — Preceding unsigned comment added by 50.54.141.59 (talk) 23:08, 22 April 2017 (UTC)
replies: text: Thanks for your comment and review on this. Please check the latest version of this article which I have updated 3 important parts with their ready-for-testing source code: Centralized Barrier, Sense-Reversal Centralized Barrier and POSIX Thread barrier functions.Anonymous Agent (talk) 17:35, 7 May 2024 (UTC)
thread_title:  Incorrect pseudocode examples 

message: This page is about thread synchronization barriers, as evidenced by its content.  
Memory barriers are not an implementation of these!
The link implies a strong technical connection between the two concepts, where there is a weak analogy at most.
If the link is just a signpost to the lost seeker if memory barrier knowledge, it should be labelled as such.
Its possible that the ambiguous naming of this page is at fault, in which case it should be renamed synchronization barrier.  —Preceding unsigned comment added by Alexbbrown (talk • contribs) 13:34, 9 July 2008 (UTC)
thread_title:  Removed link to memory barrier 

message: This page is named "barrier" and should not be used for synchronisation barriers only, but must give an overview of all kind of computer science related barriers. A "synchronization barrier" page may be created to contain more about the synchronization primitive.  —Preceding unsigned comment added by 82.228.245.190 (talk) 14:45, 8 December 2009 (UTC)
thread_title:  Added processor and compiler barrier section 

message: I have added a paragraph to indicate use of the terms "latch" and "count-down latch" to refer to specific types of barrier. I have avoided mentioning any specific implementations (C++, Java, etc), but indicative examples for those languages could be added to the article if anyone feels so inclined. I used the terms "raised" and "lowered" to refer to the states, but I see, in the article, the terms "stop", "pass", "proceed", "set", and "clear" are used to refer to the same states; I have also seen "closed" and "open" used elsewhere. If there is a de-facto convention, it may improve this article to use accepted state names. However, I believe the particular names "raised" and "lowered" are more understandable for those less familiar with concurrent or parallel computing: outside of computer science, a barrier or flag may be raised or lowered.  148.252.133.102 (talk) 14:55, 23 February 2021 (UTC)
replies: text: The "raised" and "lowered" names are misleading actually. I really don't know which one is which, and there is no explanation just next to those terms. You can imagine a physical barrier that you raise to open it, as well as one that you lower to open it. I also just spent a couple of minutes googling for any papers using this terminology and didn't find anything, but to be honest it is hard to find any consistent naming conventions, most texts just say "threads cannot proceed"/"thread is blocked" or similar. But I would really prefer to change this to "stop"/"pass" or anything that can be understood without ambiguity. TPReal (talk) 20:41, 3 November 2022 (UTC)
thread_title:  Latch and count-down latch