Re: Cache size restrictions obsolete for unrolling?

> I have a strong feeling that it all depends very much on the platform
> you're targeting. And maybe also on how much memory the loop itself
> accesses as data, that wouldn't put any more pressure on the code
> cache obviously, but if the code does not fit in the cache then the
> real data and the code will both be fighting for the same resources
> (secondary cache, main memory). I haven't tested it at all, but it
> could matter, right?


Yes, this seems reasonable for systems with separate data caches and
even more when both data and code are in the same cache. However, in
my system there is no data cache and all data is placed in a fast
memory close to the processor called scratch pad memory. So, what do
you think when data is not competing with the code for the memory
system? Can I-cache misses be neglected at the cost of more aggressive
optimization?

Return to the comp.compilers page.
Search the comp.compilers archives again.