en Copyright 2015 Java http://172.16.0.5:8080/history/llvm-project-15.0.7/llvm/test/CodeGen/ARM/fence-singlethread.ll#bb80d3e1 Enhance synchscope representation OpenCL 2.0 introduces the notion of memory scopes in atomic operations to global and local memory. These scopes restrict how synchronization is achieved, which can result in improved performance. This change extends existing notion of synchronization scopes in LLVM to support arbitrary scopes expressed as target-specific strings, in addition to the already defined scopes (single thread, system). The LLVM IR and MIR syntax for expressing synchronization scopes has changed to use *syncscope("<scope>")*, where <scope> can be "singlethread" (this replaces *singlethread* keyword), or a target-specific name. As before, if the scope is not specified, it defaults to CrossThread/System scope. Implementation details: - Mapping from synchronization scope name/string to synchronization scope id is stored in LLVM context; - CrossThread/System and SingleThread scopes are pre-defined to efficiently check for known scopes without comparing strings; - Synchronization scope names are stored in SYNC_SCOPE_NAMES_BLOCK in the bitcode.Differential Revision: https://reviews.llvm.org/D21723llvm-svn: 307722 List of files: /llvm-project-15.0.7/llvm/test/CodeGen/ARM/fence-singlethread.ll Tue, 11 Jul 2017 22:23:00 +0000 Konstantin Zhuravlyov <kzhuravl_dev@outlook.com> http://172.16.0.5:8080/history/llvm-project-15.0.7/llvm/test/CodeGen/ARM/fence-singlethread.ll#46e58354 ARM: lower "fence singlethread" to a pure compiler barrier.Single-threaded fences aren't required to provide any synchronization withother processing elements so there's no need for a DMB. They should still be abarrier for compiler optimizations though.llvm-svn: 300904 List of files: /llvm-project-15.0.7/llvm/test/CodeGen/ARM/fence-singlethread.ll Thu, 20 Apr 2017 21:56:52 +0000 Tim Northover <tnorthover@apple.com>