This is a patch implementing builtins for an atomic exchange with full,
acquire, and release memory barrier semantics. It is similar to
__sync_lock_test_and_set(), but the target does not have the option of
implementing a reduced functionality of only implementing a store of 1.
Also, unlike _
On Mon, 23 May 2011, Aldy Hernandez wrote:
> This is a patch implementing builtins for an atomic exchange with full,
> acquire, and release memory barrier semantics. It is similar to
> __sync_lock_test_and_set(), but the target does not have the option of
> implementing a reduced functionality of
Hi,
tested x86_64-linux, committed to mainline.
Paolo.
//
2011-05-23 Paolo Carlini
* include/bits/streambuf_iterator.h: Use noexcept per the FDIS.
(istreambuf_iterator<>::istreambuf_iterator(const
istreambuf_iterator&), ~istreambuf_iterator()): A
Hi
http://gcc.gnu.org/ml/gcc-patches/2011-03/msg01973.html
Use ldrd and strd to access two consecutive words
http://gcc.gnu.org/ml/gcc-patches/2011-05/msg00490.html
Compute attr length for thumb2 insns
http://gcc.gnu.org/ml/gcc-patches/2011-05/msg01092.html
Replace 32 bit instructions with 16 bi
In this case, the copy constructor is trivial, so we don't complain
about having a non-trivial copy constructor. But we should still be
doing the lvalue-rvalue conversion, which strictly speaking involves a
copy constructor call.
Tested x86_64-pc-linux-gnu, applying to trunk.
commit a3138b146
It occurred to me today that I could use current_class_name rather than
TYPE_IDENTIFIER (current_class_type).
Tested x86_64-pc-linux-gnu, applied to trunk.
commit d40ebc9ef2be8ab9b4d71410d9797442b2c16d9a
Author: Jason Merrill
Date: Mon May 23 15:23:42 2011 -0400
* pt.c (tsubst_copy_and
> gcc/
> * libgcc2.h (__NW, __NDW): Define using a __gnu_ prefix if
> LIBGCC2_GNU_PREFIX is defined.
> (__N): New macro.
> (__powisf2, __powidf2, __powitf2, __powixf2, __bswapsi2, __bswapdi2,
> __mulsc3, __muldc3, __mulxc3, __multc3, __divsc3, __divdc3, __divxc3,
On Mon, 23 May 2011 22:23:01 +0200
Richard Guenther wrote:
[...]
> plugin header? what's that?
[...]
The headers made available to and installed for plugins,
thru the PLUGIN_HEADERS variable of the gcc/Makefile.in near line 4572
After installation, plugin developers can access them because the
101 - 108 of 108 matches
Mail list logo