ply!
>danxiaoqiang
>
>
>
> --
> View this message in context:
> http://gcc.1065356.n5.nabble.com/A-GGC-related-question-tp988400p988645.html
> Sent from the gcc - patches mailing list archive at Nabble.com.
On 11/22/2013, 8:04 PM, dxq wrote:
fixing SMS, do you mean that we only modify the SMS pass?
You don't need loop unrolling when you have a good software pipelining
and loop vectorization. A good software pipelining can see through any
number of iterations and has no problems with code cache l
cc crashes down.
That's what I can think of. you know, it's a very big and hard work. do
you have any suggestions about our current solution?
thanks for your reply!
danxiaoqiang
--
View this message in context:
http://gcc.1065356.n5.nabble.com/A-GGC-related-question-tp988
On 11/22/2013, 8:08 AM, dxq wrote:
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
of_compilation, but if
inlining happens, it crashes down. if the functions are independent, is it
safe to force to do GGC after tree_rest_of_compilation?
Brs,
Thanks!
danxiaoqiang
--
View this message in context:
http://gcc.1065356.n5.nabble.com/A-GGC-related-question-tp988400.htm
