Coding Neon Kernels for the Cortex-A53
destevez.net
Coding Neon Kernels for the Cortex-A53
1–10 of 11 posts
Re: Coding Neon Kernels for the Cortex-A53
#2A53 is not a great core, and seemingly no compiler targets it well. Back at el goog, ChromeOS team had an intern who used a cycle-accurate model of it to find that android's AOT compiler produced shit code for it when multiplies were involved. A small patch to the AOT compiler produced measurable perf improvement in most android workloads on A53, costing no perf on A57/A72. This patch was, of course, not shipped (politics).
Re: Coding Neon Kernels for the Cortex-A53
#3A53 is not a great core, and seemingly no compiler targets it well. Back at el goog, ChromeOS team had an intern who used a cycle-accurate model of it to find that android's AOT compiler produced shit code for it when multiplies were involved. A small patch to the AOT compiler produced measurable perf improvement in most android workloads on A53, costing no perf on A57/A72. This patch was, of course, not shipped (pol…
Could you expand on the "politics" part? I can't imagine the reason why. I mean, if you had said "suits thought this wasn't business relevant" or something, I'd have believed it.
Re: Coding Neon Kernels for the Cortex-A53
#4A53 is not a great core, and seemingly no compiler targets it well. Back at el goog, ChromeOS team had an intern who used a cycle-accurate model of it to find that android's AOT compiler produced shit code for it when multiplies were involved. A small patch to the AOT compiler produced measurable perf improvement in most android workloads on A53, costing no perf on A57/A72. This patch was, of course, not shipped (pol…
Could you expand on the "politics" part? I can't imagine the reason why. I mean, if you had said "suits thought this wasn't business relevant" or something, I'd have believed it.
The intern was in the ChromeOS team, the fix would have needed to go into android. Those two teams were always in a bit of "stay in your lane, buddy" relationship.
Re: Coding Neon Kernels for the Cortex-A53
#5Earlier quoted context omitted.
Could you expand on the "politics" part? I can't imagine the reason why. I mean, if you had said "suits thought this wasn't business relevant" or something, I'd have believed it.
The intern was in the ChromeOS team, the fix would have needed to go into android. Those two teams were always in a bit of "stay in your lane, buddy" relationship.
I continue to maintain that Google should adopt negative peer bonuses
Re: Coding Neon Kernels for the Cortex-A53
#6Earlier quoted context omitted.
The intern was in the ChromeOS team, the fix would have needed to go into android. Those two teams were always in a bit of "stay in your lane, buddy" relationship.
I continue to maintain that Google should adopt negative peer bonuses
"The peer malus" - Frederic Beal
Re: Coding Neon Kernels for the Cortex-A53
#7Earlier quoted context omitted.
Could you expand on the "politics" part? I can't imagine the reason why. I mean, if you had said "suits thought this wasn't business relevant" or something, I'd have believed it.
The intern was in the ChromeOS team, the fix would have needed to go into android. Those two teams were always in a bit of "stay in your lane, buddy" relationship.
I thought the fabled monorepo was supposed to prevent this?
Re: Coding Neon Kernels for the Cortex-A53
#8Earlier quoted context omitted.
The intern was in the ChromeOS team, the fix would have needed to go into android. Those two teams were always in a bit of "stay in your lane, buddy" relationship.
I thought the fabled monorepo was supposed to prevent this?
IIRC, both Android and Chrome(OS) upstream are not in the google3 monorepo.
Re: Coding Neon Kernels for the Cortex-A53
#9Earlier quoted context omitted.
The intern was in the ChromeOS team, the fix would have needed to go into android. Those two teams were always in a bit of "stay in your lane, buddy" relationship.
I continue to maintain that Google should adopt negative peer bonuses
And that will result increased tension between the teams “downvoting each other”.
Maybe this way Google will truly become a Microsoft-type of company.
Re: Coding Neon Kernels for the Cortex-A53
#10A53 is not a great core, and seemingly no compiler targets it well. Back at el goog, ChromeOS team had an intern who used a cycle-accurate model of it to find that android's AOT compiler produced shit code for it when multiplies were involved. A small patch to the AOT compiler produced measurable perf improvement in most android workloads on A53, costing no perf on A57/A72. This patch was, of course, not shipped (pol…
The article also mentions how the llvm-mca is inaccurate for the A53. And furthermore LLVM compilers will do poorly
"...any compiler that is using LLVM to optimize machine code (such as the Rust compiler or clang) will not do very well for the A53, since it’s essentially trying to optimize code using a wrong CPU model. "