Sun,
I have a new compile-time testing for whole kernel build, this time
we build on a new machine
with
Intel(R) Xeon(R) CPU E5310 @ 1.60GHz, 32190M Memory
Linux pluto 2.6.16.60-0.21-smp #1 SMP Tue May 6 12:41:02 UTC 2008 x86_64
x86_64 x86_64 GNU/Linux
opt build compiler, single
debug build compiler has so many assertions and verification checks
that the total compile time is totally skewed.
Sun
On Wed, Jan 11, 2012 at 11:43 AM, Gang Yu wrote:
> I have a whole build for the linux kernel(the intensive using of ASM
> statements)
>
> We find
>
> 428777 tries for copy propra
I have a whole build for the linux kernel(the intensive using of ASM
statements)
We find
428777 tries for copy propragation for vars inside ASM_INPUT, in 3845 files
, 28609 pus
12560 successfuly copy proped in 1374 files, 3060 pus
The total build time in XEON x5570(2.93G, 24020M memory) worksta
om: Sun Chan [mailto:sun.c...@gmail.com]
> Sent: Tuesday, January 10, 2012 6:00 AM
> To: Ye, Mei
> Cc: open64-devel
> Subject: Re: [Open64-devel] Review request for fix bug787[WOPT]
>
> I wonder what the behavior at O0 for this bug?
> Sun
>
> On Tue, Jan 10, 2012 at 8:28 AM, Su
It passes at -O0 and at -O1. Fails at -O2.
Regards,
Shivaram
-Original Message-
From: Sun Chan [mailto:sun.c...@gmail.com]
Sent: Tuesday, January 10, 2012 6:00 AM
To: Ye, Mei
Cc: open64-devel
Subject: Re: [Open64-devel] Review request for fix bug787[WOPT]
I wonder what the behavior at
06, 2012 9:55 PM
>> To: Gang Yu
>> Cc: open64-devel
>> Subject: Re: [Open64-devel] Review request for fix bug787[WOPT]
>>
>> this fix looks better. i am still a bit worry about regressions
>> (performance). Have you checked perf regression with this change?
&g
s disabled upstream.
>
> -Mei
>
> -Original Message-
> From: Sun Chan [mailto:sun.c...@gmail.com]
> Sent: Friday, January 06, 2012 9:55 PM
> To: Gang Yu
> Cc: open64-devel
> Subject: Re: [Open64-devel] Review request for fix bug787[WOPT]
>
> this fix lo
Gang Yu
Cc: open64-devel
Subject: Re: [Open64-devel] Review request for fix bug787[WOPT]
this fix looks better. i am still a bit worry about regressions
(performance). Have you checked perf regression with this change?
Sun
On Sat, Jan 7, 2012 at 1:36 PM, Gang Yu wrote:
> Hi,
>
> I have a new
copy prop is not always a win. I'd like to see some performance
testing. If possible, compile time testing. it is known to cause
longer compile time also (it is basically a n^^2 algo
Sun
On Sat, Jan 7, 2012 at 5:28 PM, Gang Yu wrote:
> Thanks for the review.
>
> The new patch introduces more copy
Thanks for the review.
The new patch introduces more copy-props in the code. so, personally I
think if it will not introduce performance regression.
We test the whole kernel build, besides fix bug787, it does not introduce
new failures.
Regards
Gang
On Sat, Jan 7, 2012 at 1:54 PM, Sun Chan wr
this fix looks better. i am still a bit worry about regressions
(performance). Have you checked perf regression with this change?
Sun
On Sat, Jan 7, 2012 at 1:36 PM, Gang Yu wrote:
> Hi,
>
> I have a new fix for the bug787, the cut-down case from Rao(thanks) is as
> follows:
>
> extern int main(
Hi,
I have a new fix for the bug787, the cut-down case from Rao(thanks) is as
follows:
extern int main(int argc)
{
int res1;
int val0,val1;
val1=100;
if(1)
{
asm("bswapl %0" : "=r" (val0) : "0" (val1));
res1=val0;
}
val0=res1;
asm("bswapl %0" : "=r" (val1) : "0" (val0));
12 matches
Mail list logo
