Re: FRE may run out of memory

2014-02-19 Thread dxq
Richard Biener-2 wrote > On Fri, Feb 14, 2014 at 3:50 AM, dxq < > ziyan01@ > > wrote: > > What compiler version did you check? I think that 4.8 has improvements > for 1. and 2. (SMS is unmaintained). Note that we only spent time to > make -O1 behave sanely wit

Re: FRE may run out of memory

2014-02-13 Thread dxq
Richard Biener-2 wrote > On Sat, Feb 8, 2014 at 8:29 AM, dxq < > ziyan01@ > > wrote: >> hi all, >> >> We found that gcc would run out of memory on Windows when compiling a >> *big* >> function (10 lines). >> >> More investigation

FRE may run out of memory

2014-02-07 Thread dxq
hi all, We found that gcc would run out of memory on Windows when compiling a *big* function (10 lines). More investigation shows that gcc crashes at the function *compute_avail*, in tree-fre pass. *compute_avail* collects information from basic blocks, so memory is allocated to record infor

memory leak in reorg_loops

2014-01-02 Thread dxq
1D6BC: execute_pass_list (passes.c:2153) should loop_stack be freed at the end of reorg_loops? please confirm! if it's true, commit for me, thanks! free_loops (loops); + bitmap_obstack_release (&loop_stack); if (dump_file) print_rtl (dump_file, get_insns ()); thanks! dxq

questions about COND_EXEC and SMS

2013-12-05 Thread dxq
hi all, *We found that COND_EXEC is better than IF_THEN_ELSE when used as expressing condition move insns, because in sched, IF_THEN_ELSE insn has a dependence on itself, and COND_EXEC has not. * Besides, IF_THEN_ELSE is not good for SMS. some backend (frv) expands condition move as IF_THEN_ELSE

Re: A GGC related question

2013-11-22 Thread dxq
fixing SMS, do you mean that we only modify the SMS pass? if so, the problem we have to solve: * how to make unroll and sms work together? calling unroll pass in sms, but it would be needed more passes such as web, and it's perfect to rerun all the passes between unroll and sms. * unroll and

A GGC related question

2013-11-22 Thread dxq
hi, I'm doing a work to make unroll, doloop, and sms pass work together as following way: * before the first unroll pass, duplicate all global information such as insn chain and CFG as backup. * unroll with factor = 1, go on to finish sms, and record the result of swp, ii, loop count etc *