9 ms·
Apple's M4 has reportedly adopted the ARMv9 architecture
- saagarjha 2y agoI do find it amusing that journalists never go beyond Twitter for discussion on this because this was all being confirmed on Mastodon days before any of the posts in the article
- zarathustreal 2y agoThing is, normal people don’t really like interacting with the kind of person that would have jumped over to Mastodon. Zeal is insufferable most of the time.
- saagarjha 2y agoWell, unfortunately, the kind of person who is an expert on SME is on Mastodon. So if you're writing an article on it, you should probably go to them instead of tech influencers who recycle content on Twitter.
- joshstrange 2y agoI’m fairly certain that staying on (or joining) Twitter shows just about the same amount of “zeal” as leaving for Mastodon/BlueSky/Threads. Or put another way, I find people on Twitter to be insufferable. It’s not a secret that a large portion of actually technical people (not tech influencers) left Twitter for Mastodon. So the people on Twitter may be more polished turds but are turds nonetheless. Full disclosure: I still use my Twitter for customer support because that’s all it’s good for at this point IMHO. I also don’t regularly read mastodon but it’s where the people I care about are and when I post (rarely) that’s where I do it.
- TiredOfLife 2y agoAccording to https://news.ycombinator.com/item?id=40465451 https://news.ycombinator.com/item?id=40465451 they have not switched to armv9. So I am curious what they were confirming?
- saagarjha 2y agoSME and streaming SVE. In fact I was going to include “…and nobody seems to have good evidence of ARMv9 support” but I figured my comment was enough as it was ;)
- alberth 2y agoCan someone ELI5 the significance.
- deleted 2y ago[deleted]
- saagarjha 2y agoApple added some standard vector processing instructions
- capl 2y agoHmm, I was thinking of buying an M3 Pro 16” this summer, but maybe I should wait then
- Waterluvian 2y agoApple’s tempo is so regular that this has been a problem my entire adult life. I’ll buy a little later. I’ll buy a little later!
- capl 2y agoHehe yeah, same when I think about it… I guess best thing to do is buy on launch and update every 2-5 years.
- spacebanana7 2y agoIf staying on the latest model isn’t important to you, there’s significant cost savings to be made from just buying the previous version.
- asddubs 2y agoso wait for M5 to buy M4
- MediumOwl 2y agoIt entirely depends how long you keep your devices. I try to keep my iPhones until release year + 6, so I would need the price of a previous version to be reduced by more than 1/6th on a new version release, which is usually not the case.
- spacebanana7 2y agoSimilar to cars, most depreciation happens in the first year. So owning a device for 6 years between age 1 and 7 will generally have a lower cost than owning a device between age 0 and 6. For Apple products it’s generally feasible to effectively buy first hand devices aged 1+ because they’re still available for sale (at least in some retailers) after a new edition is released.
- meindnoch 2y agoSo binary sizes are going to double?
- phkahler 2y ago>> So binary sizes are going to double? If you're already supporting 2 arch it will only increase by 50 percent to support a 3rd ;-)
- JKCalhoun 2y agoAnd you'd like to think the binaries are still not the largest component of an app contributing to the file size. But who knows these days.
- DaiPlusPlus 2y agoIts the static-linking of the Swift runtime - it’s incredibly inelegant.
- saagarjha 2y agoThe Swift runtime is not statically linked on Apple’s platforms
- kenferry 2y ago(Anymore)
- saagarjha 2y agoI don't think it ever was?
- saurik 2y agoI do also believe it wasn't ever technically "statically linked", but the dynamic libraries were separately distributed as part of every app (and so I'd think the semantic slippage acceptable given the context). This has tons of advantages, but prevented Swift from being used in Apple libraries.
- deleted 2y ago[deleted]
- Aaargh20318 2y agoThe most incredible thing about the new iPads is that even with the crazy fast M4 chip MS Teams manages to crawl to a halt. Clearly it takes all the engineering skills of the largest and most valuable software company in the world to make text entry go at about 1 fps on a chip as powerful as the M4.
- deleted 2y ago[deleted]
- akmarinov 2y agoThat's usually what cross platform at an enterprise company at scale gets you
- chongli 2y agoMS Teams is by far the worst piece of software I’ve ever used. It is ungodly slow and it just gets slower the more you use it. I believe it is actually hitting the server to update the online/away status light for every single message in a conversation. If you turn off all the status update stuff in the settings then the software speeds up dramatically. Another thing you can do is find the folder where it caches everything and just trash the entire thing. Somehow, they’ve managed to make caching slow everything down rather than provide a speed up.
- Dalewyn 2y agohttps://en.wikipedia.org/wiki/Wirth%27s_law https://en.wikipedia.org/wiki/Wirth%27s_law
- treyd 2y agoWhy is that not at least done asynchronously? I thought part of the whole narrative of shipping these new terrible pieces of software as standalone Google Chrome instances was that it makes it easier to spawn async JS workers for background tasks and whatnot?
- chongli 2y ago
- ko27 2y agoIt seems that M4 was overhyped. Almost of all of the performance improvements, in Geekbench for example, comes from new instructions that most apps won't use, and even if they do they might end up using the faster GPU/NPU for those tasks. https://twitter.com/toniievych/status/1788596920627118248 https://twitter.com/toniievych/status/1788596920627118248
- talldayo 2y ago> Technically, Intel has its matrix extensions (Intel AMX), but Geekbench does not support it. Lmao, and people say Geekbench isn't biased towards ARM
- ribit 2y agoGeekbench supports Intel AMX and AVX-512. This is all in GB documentation.
- dragonelite 2y agoMakes one wonder has the apple miracle mostly been first the transition to ARM and having access to TSMC highest end nodes before the rest even comes into the picture. But im glad new competition is coming from qualcomm x elite and Huawei with their Kirin and Ascends chips. Hopefully ARMsrace will be more interesting to follow than the x64 race between intel and AMD.
- hajile 2y agoOryon was designed to compete with M1 then the clockspeeds were ramped up to compete with M2. M3 clearly beat it out and M4 has only furthered that lead. Oryon will still probably beat x86 designs massively in performance per watt which is pretty much the most important metric for most people anyway (as most people use laptops). EDIT: your username `dragonelite` is quite interesting. You joined 2019, but the coincidence is fascinating.
- sgerenser 2y agoIt’s a decent, but not revolutionary improvement. Yes, most of the gains outside of SME are coming from clock increases not IPC. I don’t know if I would call it overhyped, more like misunderstood.
- ribit 2y agoThey have not adopted ARMv9. This is still ARMv8, but with SME.
- axoltl 2y agoYep, the binaries are all arm64e.
- saagarjha 2y agoThis doesn’t really say much
- hajile 2y agoARMv9.0 is very similar to ARMv8.5 (9.0 supersets 8.5 with SVE2, TME, TLA, and CCA), so it's not a massive deal. SME implies v8.7 which is basically identical to v9.2 except for those couple extensions previously mentioned. I wonder if there is licensing at play though. Apple may have gotten a really great licensing deal on ARMv8 that they wouldn't be offered for ARMv9.
- ribit 2y agoMy guess is that Apple is simply not interested in some of the ARMv9 features. They are not eager to implement SVE and the se Ure virtualization features are probably not that relevant to them.
- skavi 2y agoDoes anyone have insight into why arm CPU vendors seem so hesitant about implementing SVE2? ~They seem~ *Apple seems to have no issue with SSVE2 or SME. Edit: Only Apple has implemented SSVE and SME I think.
- hajile 2y agoSVE2 is an extension on top of SVE which some stuff already implements. The issue is more likely to be the politics of moving to ARMv9 than anything else. As to SVE though, I'd guess variable execution time makes the implementation require a bit of work. Normally, multi-cycle tasks have a fixed number. Your scheduler knows that MUL takes N cycles and plans accordingly. SVE seems like it should require N-M cycles depending on what is passed. That must be determined and scheduled around. This would affect the OoO parts of the core all the way from ordering through to the end of the pipeline. That's definitely bordering on new uarch territory and if that is the case, it would take 4-5 years from start to finish to implement. This would explain why all the ARMv8 guys never got around to it. ARMv9 makes it mandatory, but that was released in 2021 or so which means non-ARM implementors probably have a ways to go.
- deleted 2y ago[deleted]
- pjmlp 2y agoSo finally MTE enabled?
- saagarjha 2y agoApple’s chips have been MTE enabled for a while, it’s just turned off
- awill 2y agoWhat's so shocking about this? The Arm Cortex X2 which launched 2 years ago has ARMv9
- eyelidlessness 2y agoWhy do you assume anything is supposed to be shocking about this?
- javawizard 2y agoI'm guessing GP meant something more like: What's so newsworthy about this?
- deleted 2y ago[deleted]
- TiredOfLife 2y agoAnd what does arm reference design has to do with completely custom core?
- johnklos 2y agoARM really could've come up with better numbering / identification. I suppose it's ARM, emphasis on v, then 9, to differentiate it from ARM9, such as ARM9E-S?