- Joined
- Sep 26, 2021
- Posts
- 5,970
- Main Camera
- Sony
Speaking of the Stanford mall... [REDACTED]
Edited because I fell into the “politics” trap!
I hate that Stanford Apple store, btw. The light from the skylight makes me feel nauseous.
Speaking of the Stanford mall... [REDACTED]
I hate that Stanford Apple store, btw. The light from the skylight makes me feel nauseous.
It glows.There's something weird about that light.
It glows.
Well... it is luminous.
I think I might be feeling what Cmaier is talking about. For me it isn't nausea, but a feeling of uneasiness that I can't put my finger on.
Similarly... when Apple opened its new store in downtown Palo Alto around 12 years ago, I also felt uncomfortable. Not due to light, but to the overwhelming noise in the large space when it was full of people. A lot of that had to do with the walls, glass ceiling, and massive glass front randomly reflecting sound from people talking, in and out of phase. I'm guessing that made people talk louder, exacerbating the situation (positive feedback). Eventually Apple addressed the problem by putting trees and sound deadening material inside, which made a huge difference.
Perhaps that's what's happening at the Stanford mall store. Three sides of the building and the ceiling are massive sheets of glass, and no doubt great sound reflectors.
It’s something about the pattern of light and shadows caused by the light streaming in from above, I think.
I get an uncomfortable feeling in every Apple Store… but mostly because I get the unshakable urge to buy something.yep! i have the same problem with the “new” University Ave store. I’ve been in a lot of Apple stores around the world - paris, rome, NY, etc. Only the two in Palo Alto make me feel so uncomfortable I hate to be there. It’s something about the pattern of light and shadows caused by the light streaming in from above, I think.
A14 <=> M1 (both used Firestorm P-cores and Icestorm E-cores).
A15 <=> M2 (both used Avalanche P-cores and Blizzard E-cores).
But does that continue, such that:
A16 <=> M3?
A17 <=> M4?
A18 <=> M5??
or:
A16 <=> nothing
A17 <=> M3?
A18 <=> M4?
It’s the latter. A16 corresponds to nothing in the M-series. Though weirdly the internal alphanumeric code name for the M3-series SOC starts with H15 (as in A16) rather than 16 (as in A17 Pro), the cores are clearly the same as A17 Pro and manufactured on the same node - both M3 and A17 Pro P-core share features like a wider decode/better branch prediction than the A16 core and overall have similar performance characteristics albeit at different clocks.There used to be a correspondence between the A-series and M-series CPU cores:
A14 <=> M1 (both used Firestorm P-cores and Icestorm E-cores).
A15 <=> M2 (both used Avalanche P-cores and Blizzard E-cores).
But does that continue, such that:
A16 <=> M3?
A17 <=> M4?
A18 <=> M5??
or:
A16 <=> nothing
A17 <=> M3?
A18 <=> M4?
I ask because I've not found core names for the M3 or M4. And Ryan Smith also expressed uncertainty about this when the M3 was introduced, writing:
"The question is whether we’re looking at the CPU cores from the recently launched A17 SoC, or the CPU cores from the A16 (Everest and Sawtooth). The A17 is the more likely candidate, especially since Apple already has working IP for N3B. But strictly speaking, we don’t have enough information to rule out the A16 CPU cores at this time; especially as Apple is not offering any guidance on the architectural improvements that the M3 family’s CPU cores offer over the M2."
Apple Announces M3 SoC Family: M3, M3 Pro, and M3 Max Make Their Marks
www.anandtech.com
The way stuff works, you can mostly guess that cores are tied to a process. M2 was N5P, A16 on N4P, M3 and A17 both on N3B, M4 and A18 on N3E. M3/A17 are ARMv8.6, as opposed to M4/A18 which are v9.2 (not really that big a jump as 8.6 is basically the same as 9.1).
So, yeah, it looks like A16 is an orphan.
I would assume that stating Ax or Mx is ARMv# is a user-side compatibilty claim: code built for 8.6 will run on the M3, but if you want to run code compiled for 9.1, you need M4. There is very little difference – perhaps a handful of arcane ops, plus SVE2/SME – because a large fraction of 9.n is on the system side, and of course, Apple has some unpublished capabilities.the whole exact ARM version is a bit ... unclear
@leman had a detailed discussion with a bunch of people about this I think at the other place and I honestly can't remember what they concluded about whether M4 counts as Arm v9 (I think it does?) - I only remember that the definitions of 8 vs 9 was a lot murkier than I, or anyone in that conversation, had realized before the conversation started - eg a lot of stuff we assumed as required like SVE was actually optional, the actual differentiation was something else, it was a lot different than what I had expected it to be. @leman would probably remember better than me as he really dug into it.I would assume that stating Ax or Mx is ARMv# is a user-side compatibilty claim: code built for 8.6 will run on the M3, but if you want to run code compiled for 9.1, you need M4. There is very little difference – perhaps a handful of arcane ops, plus SVE2/SME – because a large fraction of 9.n is on the system side, and of course, Apple has some unpublished capabilities.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.