Displaying 7 results from an estimated 7 matches for "__builtin_memory_barrier".
2008 Sep 16
4
[LLVMdev] llvm memory barrier as a builtin
...tion as a built-in
from clang, which means that I need a name for it. In gcc, I see names
like __builtin_ia32_mfence but those refers to X86 SSE instruction
that we support. I don't see a gcc name that has the same semantics
as our barrier instruction. For a name, I was thinking of
__builtin_memory_barrier or __builtin_llvm_memory_barrier. Does
anyone object of adding it as built-in or have a better idea for a name?
-- Mon Ping
2008 Sep 17
2
[LLVMdev] llvm memory barrier as a builtin
...means that I need a name for it. In gcc, I see
>> names
>> like __builtin_ia32_mfence but those refers to X86 SSE instruction
>> that we support. I don't see a gcc name that has the same semantics
>> as our barrier instruction. For a name, I was thinking of
>> __builtin_memory_barrier or __builtin_llvm_memory_barrier. Does
>> anyone object of adding it as built-in or have a better idea for a
>> name?
>
> __sync_synchronize is the gcc builtin for a memory barrier.
>
> Andrew
> _______________________________________________
> LLVM Developers maili...
2008 Sep 17
0
[LLVMdev] llvm memory barrier as a builtin
...from clang, which means that I need a name for it. In gcc, I see names
> like __builtin_ia32_mfence but those refers to X86 SSE instruction
> that we support. I don't see a gcc name that has the same semantics
> as our barrier instruction. For a name, I was thinking of
> __builtin_memory_barrier or __builtin_llvm_memory_barrier. Does
> anyone object of adding it as built-in or have a better idea for a name?
What are the semantic differences?
Thanks,
Duncan.
2008 Sep 17
1
[LLVMdev] llvm memory barrier as a builtin
...ang, which means that I need a name for it. In gcc, I see names
>> like __builtin_ia32_mfence but those refers to X86 SSE instruction
>> that we support. I don't see a gcc name that has the same semantics
>> as our barrier instruction. For a name, I was thinking of
>> __builtin_memory_barrier or __builtin_llvm_memory_barrier. Does
>> anyone object of adding it as built-in or have a better idea for a name?
>
> What are the semantic differences?
As far as I know, there isn't a difference, just that the intrinsic
isn't platform-specific. I think SSE2 mfence is equival...
2008 Sep 17
0
[LLVMdev] llvm memory barrier as a builtin
...-in
> from clang, which means that I need a name for it. In gcc, I see names
> like __builtin_ia32_mfence but those refers to X86 SSE instruction
> that we support. I don't see a gcc name that has the same semantics
> as our barrier instruction. For a name, I was thinking of
> __builtin_memory_barrier or __builtin_llvm_memory_barrier. Does
> anyone object of adding it as built-in or have a better idea for a name?
__sync_synchronize is the gcc builtin for a memory barrier.
Andrew
2008 Sep 17
0
[LLVMdev] llvm memory barrier as a builtin
...name for it. In gcc, I see
>>> names
>>> like __builtin_ia32_mfence but those refers to X86 SSE instruction
>>> that we support. I don't see a gcc name that has the same semantics
>>> as our barrier instruction. For a name, I was thinking of
>>> __builtin_memory_barrier or __builtin_llvm_memory_barrier. Does
>>> anyone object of adding it as built-in or have a better idea for a
>>> name?
>> __sync_synchronize is the gcc builtin for a memory barrier.
>>
>> Andrew
>> _______________________________________________
>>...
2008 Sep 18
1
[LLVMdev] llvm memory barrier as a builtin
...t;> names
>>>> like __builtin_ia32_mfence but those refers to X86 SSE instruction
>>>> that we support. I don't see a gcc name that has the same
>>>> semantics
>>>> as our barrier instruction. For a name, I was thinking of
>>>> __builtin_memory_barrier or __builtin_llvm_memory_barrier. Does
>>>> anyone object of adding it as built-in or have a better idea for a
>>>> name?
>>> __sync_synchronize is the gcc builtin for a memory barrier.
>>>
>>> Andrew
>>> _________________________________...