I'm seeing a lot of testsuite failures on powerpc-linux, some of
which are locking related. For example:
WARNING: Program timed out.
FAIL: libgomp.c/atomic-10.c execution test
This one fails in f3() here:
#pragma omp atomic
z4 *= 3;
z4 is an unsigned char, so we hit the QImode case in
rs60
We are aware that the TM language constructs should be documented in
extend.texi. However, the most recent public version of the C++ TM
specification document is outdated, and a new version is supposed to be
released in a few weeks.
Therefore, we'd like to wait until the release of the new specif
On Thu, Nov 17, 2011 at 03:14:57PM +0100, Torvald Riegel wrote:
> We are aware that the TM language constructs should be documented in
> extend.texi. However, the most recent public version of the C++ TM
> specification document is outdated, and a new version is supposed to be
> released in a few
On Thu, 2011-11-17 at 17:22 +0100, Andi Kleen wrote:
> On Thu, Nov 17, 2011 at 03:14:57PM +0100, Torvald Riegel wrote:
> > We are aware that the TM language constructs should be documented in
> > extend.texi. However, the most recent public version of the C++ TM
> > specification document is outda
Gerald, I've been searching for the release criteria pages for various
releases. I haven't found anything. I was expecting to find them as
top-level links on the home page.
Should I prepare a patch? Or should I have looked in a different place?
Thanks. Diego.
On Thu, Nov 17, 2011 at 7:27 PM, Diego Novillo wrote:
>
> Gerald, I've been searching for the release criteria pages for various
> releases. I haven't found anything. I was expecting to find them as
> top-level links on the home page.
>
> Should I prepare a patch? Or should I have looked in a d
On 11-11-17 11:19 , Richard Guenther wrote:
They are release specific - in gcc-MAJOR.MINOR/criteria.html. Especially
the list of primary and secondary targets may vary. It would be
certainly useful
to have a "next upcoming release" link on the main page, pointing to
gcc-4.7/index.html. But we
On Thu, Nov 17, 2011 at 8:19 PM, Richard Guenther
wrote:
> On Thu, Nov 17, 2011 at 7:27 PM, Diego Novillo wrote:
>>
>> Gerald, I've been searching for the release criteria pages for various
>> releases. I haven't found anything. I was expecting to find them as
>> top-level links on the home pag
Hi Diego,
On Thu, 17 Nov 2011, Diego Novillo wrote:
> Gerald, I've been searching for the release criteria pages for various
> releases. I haven't found anything. I was expecting to find them as
> top-level links on the home page.
the release criteria are there, cf.
> ls ~/wwwdocs/htdocs/*/
On 11/17/2011 12:37 AM, Alan Modra wrote:
> - oldval = convert_modes (SImode, mode, oldval, 1);
> + oldval = gen_reg_rtx (SImode);
> + convert_move (oldval, orig, 1);
>oldval = expand_simple_binop (SImode, ASHIFT, oldval, shift,
> oldval, 1,
Snapshot gcc-4.5-2017 is now available on
ftp://gcc.gnu.org/pub/gcc/snapshots/4.5-2017/
and on various mirrors, see http://gcc.gnu.org/mirrors.html for details.
This snapshot has been generated from the GCC 4.5 SVN branch
with the following options: svn://gcc.gnu.org/svn/gcc/branches
On Thu, Nov 17, 2011 at 3:25 PM, Richard Henderson wrote:
> On 11/17/2011 12:37 AM, Alan Modra wrote:
>> - oldval = convert_modes (SImode, mode, oldval, 1);
>> + oldval = gen_reg_rtx (SImode);
>> + convert_move (oldval, orig, 1);
>> oldval = expand_simple_binop (SImode, ASHIF
On 11/17/2011 02:34 PM, David Edelsohn wrote:
> On Thu, Nov 17, 2011 at 3:25 PM, Richard Henderson wrote:
>> On 11/17/2011 12:37 AM, Alan Modra wrote:
>>> - oldval = convert_modes (SImode, mode, oldval, 1);
>>> + oldval = gen_reg_rtx (SImode);
>>> + convert_move (oldval, orig, 1);
>
2011/11/18 Richard Guenther :
> On Thu, Nov 17, 2011 at 6:49 AM, Yuehai Du wrote:
>> 2011/11/17 Richard Guenther :
>>> On Wed, Nov 16, 2011 at 12:28 PM, Eric Botcazou
>>> wrote:
> Huh, IVOPTs should never cause a different size memory read. I wonder
> if the original issue would still r
¿ÉÒÔ´ú¿ª¸÷ÏîË°~~Ʊ
ÁªÏµµç»°£»13713763916
ÁªÏµÈË £» ÕÅ ÏÈ Éú
15 matches
Mail list logo
