4 ms·
That could be interesting. I remember reading a report here years ago about a funny bug that was caused by the big and little cores having different endianness.
by spockz 5y ago
That could be interesting. I remember reading a report here years ago about a funny bug that was caused by the big and little cores having different endianness. Indeed the process would start on one core, process some data, get scheduled to the other core and boom, weird output. Does someone recall the story?
- lttlrck 5y agoHaha. That sounds like a joke playing off the BIG.little name. I'd like to read about that.
- spockz 5y agoIndeed. But apparently I was mistaken. It was the story about the different cache lines on the Exynos.
- adrian_b 5y agoThat seems like a too stupid bug to have existed in a production system. However, there was a real problem a few years ago with some Samsung Exynos processors, where the cache line size was different between the big and the little cores. A few programs made assumptions about the cache line size and had weird behavior after starting on one kind of core, then being migrated on the other kind of core.
- cesarb 5y agoYou're probably remembering the bug where the big and little cores had different cache line sizes (https://www.mono-project.com/news/2016/09/12/arm64-icache/ https://www.mono-project.com/news/2016/09/12/arm64-icache/).
- spockz 5y agoWow. I mis remembered that quite spectacularly. Whoops.
- abbeyj 5y agohttps://medium.com/@niaow/a-big-little-problem-a-tale-of-big-little-gone-wrong-e7778ce744bb https://medium.com/@niaow/a-big-little-problem-a-tale-of-big...