On Feb 26, 2010, at 12:48 PM, Daniel Ehrenberg wrote: > The compiler already allows this, through 'foldable' and 'flushable' > declarations. They are used in the high-level optimizer's constant > folding and dead code elimination transformations, respectively. Loop > fusion would require a substantial reorganization of the compiler, > with an intermediate representation that represents map directly, > rather than its inlined form. I'm not sure if this would really be > possible as long as map uses call and not call(.
Instead of making the compiler deal with map and friends, maybe an object oriented approach would work, taking advantage of combinator inlining and object unboxing so that composing special map, filter, etc. objects built optimized loops. -Joe ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ Factor-talk mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/factor-talk
