> you have to optimize the code for a new CPU [...]. [...] if you have a new CPU
> core, you have to optimized the code for it. [...] The problem is, I don't see
> the developer (Morph or AOS) to squeeze the maximum out of this new CPUs.

With high-level programming languages it's rater the compiler which optimizes the scalar code for the respective microarchitecture if you provide the proper compiler switch(es). And indeed, because of the variety of microarchitectures, generation of optimized code is an issue also on MorphOS and OS4 as I described some time back:

https://morph.zone/modules/newbb_plus/viewtopic.php?forum=3&topic_id=7675&start=564

> An e600 core isn't the same as an e5500 or e6500 core.

Exactly. The e6500 and e5500 cores stem from the e500v1 core (via e500v2 and e500mc), which was conceived around 2001, i.e. back when G4/e600 was still going strong. So it was a parallel development for different markets with different demands than G4/e600 and never meant as e600 successor (also indicated by the smaller number).

> Do you really think, FreeScale is that silly? To develop a new core (approx. ten years later)
> and the new one is slower than the old one?

As a general note (i.e. not meant for the e6500/e5500 vs. e600 case specifically) semiconductor companies develop/release new cores that are slower than old cores of theirs all the time, especially if the new core is intended for different markets with different demands.