On 3 December 2015 at 16:46, Robert Schiele wrote:
> Keeping linaro-toolchain in the loop.
>
> Robert
>
>
> -- Forwarded message --
> From: Robert Schiele
> Date: Thu, Dec 3, 2015 at 4:44 PM
> Subject: Re: Lost upstream patch in merge from gcc-5-branch to
> linaro/gcc-5-branch
> T
On Wed, Dec 2, 2015 at 1:32 PM, Christopher Roberts
wrote:
> abe.sh in the ABE framework accepts a parameter to set the wget timeout when
> it fetches snapshots (default 10s); however that parameter has an upper
> threshold of 10 seconds (condition at line 996 only sets timeout to
> specified valu
On Wed, Dec 2, 2015 at 12:07 AM, Barry Song <21cn...@gmail.com> wrote:
> i am wondering whether ld.so will check the capbility of ARM to decide
> which version should be used.
I believe the way this works is that the kernel uses the auxiliary
vector to pass an AT_HWCAP entry to programs. AT_HWCAP
Keeping linaro-toolchain in the loop.
Robert
-- Forwarded message --
From: Robert Schiele
Date: Thu, Dec 3, 2015 at 4:44 PM
Subject: Re: Lost upstream patch in merge from gcc-5-branch to
linaro/gcc-5-branch
To: Yvan Roux
Hi Yvan,
On Thu, Dec 3, 2015 at 1:25 PM, Yvan Roux wr
Hi Robert,
This fix on gcc-5-branch doesn't apply on Linaro 5 branch, because we
have backported trunk revision 222624 (which renames maybe_fma to
coumpound_p) into it. So, our branch as the same code as trunk one
regarding aarch64_rtx_costs. Do you experiment any issues related to
this change ?
Hi,
I found that with the merge
commit ac19ac6481a3f326d9f41403f5dadab548b2c8a6
Author: Yvan Roux
Date: Wed Sep 16 10:57:42 2015 +0200
Merge branches/gcc-5-branch rev 227732.
Change-Id: I2f59904b28323b1c72a8cf1bd62c9e460d95bcea
the following branch that was within merge range on gcc
