Andrew Pinski writes:
> On Sat, Feb 2, 2013 at 5:10 PM, Jeffrey Walton wrote:
>> Thanks Andrew.
>>
>> So, it looks like I don't understand sequence points. Please forgive
>> my ignorance.
>>
>> What does C/C++ and GCC offer to ensure writes are complete before
>> reads are performed on a value i
On 03/02/13 02:10, Jeffrey Walton wrote:
Thanks Andrew.
So, it looks like I don't understand sequence points. Please forgive
my ignorance.
What does C/C++ and GCC offer to ensure writes are complete before
reads are performed on a value in a multi-threaded program?
Jeff
You are probably loo
> On 02/01/2013 12:38 AM, Jan Hubicka wrote:
> > Doing the extensions at caller side always is however IMO a preformance bug
> > in
> > GCC. We can definitly drop them at -Os, for non-PRS targets and for calls
> > within compilation unit where we know that GCC is not really producing
> > code lik
On Sun, Feb 3, 2013 at 2:47 PM, David Brown wrote:
> On 03/02/13 02:10, Jeffrey Walton wrote:
>>
>> So, it looks like I don't understand sequence points. Please forgive
>> my ignorance.
>>
>> What does C/C++ and GCC offer to ensure writes are complete before
>> reads are performed on a value in a
On 03/02/13 21:20, Jeffrey Walton wrote:
On Sun, Feb 3, 2013 at 2:47 PM, David Brown wrote:
On 03/02/13 02:10, Jeffrey Walton wrote:
So, it looks like I don't understand sequence points. Please forgive
my ignorance.
What does C/C++ and GCC offer to ensure writes are complete before
reads are
Snapshot gcc-4.8-20130203 is now available on
ftp://gcc.gnu.org/pub/gcc/snapshots/4.8-20130203/
and on various mirrors, see http://gcc.gnu.org/mirrors.html for details.
This snapshot has been generated from the GCC 4.8 SVN branch
with the following options: svn://gcc.gnu.org/svn/gcc/trunk
Are there plans to do more backports of regression fixes to 4.7 before 4.7.3?
Here is a list of bugs that have patches applied to 4.8 to fix the bug, but
which are still listed as 4.7 regressions:
48189 - ice-on-valid
55018 - wrong-code
54563 - ice-on-valid - already backported?
54974 - [arm] wr
On Sat, Feb 2, 2013 at 5:10 PM, Jeffrey Walton wrote:
>
> What does C/C++ and GCC offer to ensure writes are complete before
> reads are performed on a value in a multi-threaded program?
The write must be done using
__atomic_store(pointer, value, __ATOMIC_RELEASE);
The read must be done using
On Sun, Feb 3, 2013 at 11:47 AM, David Brown wrote:
>
> Anyway, the simplest memory barrier in gcc is :
>
> asm volatile("" ::: "memory");
That is a compilation level memory barrier, but it clearly does
nothing at the machine level.
To get a machine level (and compilation level) memory b
