On 08/08/14 09:24, Bin.Cheng wrote:
On Fri, Aug 8, 2014 at 4:05 PM, Kyrill Tkachov wrote:
On 07/08/14 10:43, Bin Cheng wrote:
Hi,
Case pr61772.c scans specific string in assembly file, and it is run for
many different option combinations. When it's tested against different
lto
option combina
On Fri, Aug 8, 2014 at 4:05 PM, Kyrill Tkachov wrote:
>
> On 07/08/14 10:43, Bin Cheng wrote:
>>
>> Hi,
>> Case pr61772.c scans specific string in assembly file, and it is run for
>> many different option combinations. When it's tested against different
>> lto
>> option combinations on targets li
On 07/08/14 10:43, Bin Cheng wrote:
Hi,
Case pr61772.c scans specific string in assembly file, and it is run for
many different option combinations. When it's tested against different lto
option combinations on targets like ARM, the generated pr61772.s may only
contain lto object content, rathe
On Thu, Aug 7, 2014 at 11:43 AM, Bin Cheng wrote:
> Hi,
> Case pr61772.c scans specific string in assembly file, and it is run for
> many different option combinations. When it's tested against different lto
> option combinations on targets like ARM, the generated pr61772.s may only
> contain lto
Hi,
Case pr61772.c scans specific string in assembly file, and it is run for
many different option combinations. When it's tested against different lto
option combinations on targets like ARM, the generated pr61772.s may only
contain lto object content, rather than assembly codes. The scanning ch