10 ms·
In the bigger picture Apple aren't really documenting anything for their new toys, which is not the end of the world but is a huge step back for openness. There
by mhh__ 6y ago
In the bigger picture Apple aren't really documenting anything for their new toys, which is not the end of the world but is a huge step back for openness. There is - as far as I can see - no long-form documentation for M1 other than patents.
I already refuse to own apple products so I don't really have any skin in the game, but consider that if microsoft were like this the blind eye would not be turned - buy our new product, everything you run is up to us, we won't document it, maybe we'll upstream the compiler, tough shit.
The fact that they can be like this is really proof that their market position is much stronger than most HNers seem to think it is.
- MichaelZuo 6y agoThe implication I assume that there would be pushback on Microsoft for doing the same would be because of the possibility of nefarious undocumented changes. What possibly nefarious things could an undocumented ISA extension do?
- mhh__ 6y agoUndocumented It's not about EEE it's about Apple taking this attitude in the first place.
- hyperman1 6y agoPresumably the next iteration of the processor can remove them and use the opcodes for something else. Apple recompiles their system library, hence is unaffected. You can't do the same so peak M1 performance is unavailable for you.
- MichaelZuo 6y agoCould those opcodes then be used for anything nefarious, or would it just restrict third parties from fully utilizing the processor?
- Someone 6y agoIf you think Apple wants to do something nefarious to users of their hardware, don’t buy or use it. If they can’t be trusted, they don’t need to add opcodes.
- MichaelZuo 6y agoWell the point of the question is trying to establish if it’s even possible in the first place. If there is no credible way, then there is no need to fear there are nefarious reasons for implementing such a change for either Apple or Microsoft, outside of restricting third parties. If there is, then it’s as you say.
- tenebrisalietum 6y agoApple can make tools that use the undocumented ISA, which they don't have to release to the public, potentially using it to develop applications with performance advantages that no one other than Apple can attain. It's similar to how Microsoft doesn't make all APIs on Windows public and uses non-public ones for various reasons--except this is in hardware. It's possible the undocumented ISA is used to speed up x86 emulation and might be kept secret due to intellectual property concerns or similar.
- emteycz 6y agoThey didn't have to open the platform for other software (OS) at all. Let's be happy with what we got.
- _underfl0w_ 6y ago> Let's be happy with what we got. Ouch. It's exactly this mentality that enables malicious actors - "it could be worse". It could always be worse, but that doesn't make it sufficient justification. Functional equivalent: "It could always be even more anticompetitive. Let's be happy with what we got."
- emteycz 6y agoEh, what? What malicious actors? What sufficient justification, and justification of what and to whom? What could be worse? What could be more anticompetitive, and competing with what exactly? I said nothing like this, your "equivalents" are from an entirely different world. I said we should be happy Apple decided to open their platform - because they didn't have to, at all. It's entirely their right to not open anything, not write any documentation, or not even allow 3rd party software at all. If you don't like it, don't buy their overpriced premium products - it's not for you. I wouldn't want my own company to be forced to do/not do stuff, so of course I don't wish that upon Apple. There are enough entirely open computing platforms that are VERY cheap to obtain and easy to use, perhaps that would be a better choice for you.
- 6y ago
- whatshisface 6y ago>The fact that they can be like this is really proof that their market position is much stronger than most HNers seem to think it is. Elsewhere on the HN front page is a computer made with a Russian internal CPU. The CPU has a custom ISA based on x86, and isn't open. The documentation is poor, and nobody has the source code for the compiler. It's also about 5 years behind the state of the art in x86. How can a product like this exist? Easy. Russia needs them for military hardware because they're not going to put Intel in their defense radar systems. The manufacturer has a niche to sell to. Instead of being 5 years behind, Apple's closed and undocumented ISA is 2 years ahead. How much moreso, if the Russian CPU can survive in the market, can they.
- mhh__ 6y agoThe Russian CPU isn't surviving in a market
- bnt 6y agoI exist there for I am?
- mhh__ 6y agoThey key word is market - The Elbrus is obviously propped up by the Russian government and it's tentacles. It's not an invalid business model but it's not a good way to measure technology.
- a1369209993 6y agoIt's not surviving in a market, because it's not in a market - it's being produced for a specific consumer, whose requirements are idiosyncratic enough[0] that the market refuses to service them. 0: a very low bar in this case, given the existence of things like Intel Management Engine, but it would be much the same if they insisted on something less justifiable like running all the CPU pins at 12-volt logic levels
- ardy42 6y ago> The Russian CPU isn't surviving in a market How so? It's actually not that different from Apple Silicon when you think about it. Apple Silicon: you only get it when you buy an iPhone, iPad, ARM Mac, etc. in the Smartphone or PC market; and it enables features that make those devices competitive. Russian Elbrus: you only get it when you buy some Russian military hardware in the defense market; and it enables features that make those devices competitive.
- ur-whale 6y ago>In the bigger picture Apple aren't really documenting anything for their new toys, This should not come as a surprise, it has always been Apple's default stance. Apple has been, is, and will very likely always be a closed ecosystem. They might sometimes appear or pretend to be open, but it's essentially good PR/marketing (e.g. stash Unix underneath a closed-source stack, call yourself open source and proceed to lure all the open source devs to the platform).
- Someone 6y agoI think it’s more a sign of the times than Apple being Apple that they don’t tell you what hardware you buy when you buy one of their systems or how it is connected. Television manuals used to contain hardware schematics, car manuals used to be way more detailed, etc. Apple also had detailed info on their hardware. The Apple II reference manual had schematics, mapped it to the PCB, described what each part did, described 6502 assembly and had an assembly listing of the monitor ROM. The only thing missing to build a copy, I think, was an assembly listing of the Basic interpreter. The phone book edition of Inside Macintosh also had info on the hardware, but a lot less of it.
- userbinator 6y agoThe keyword being had, but Apple has always been on the more closed side --- Inside Macintosh was far more pretty but overall less informative than the corresponding IBM PC Technical Reference books.
- noizejoy 6y agoAnd Apple is still making Macs, while IBM gave up making PCs quite a while ago. Who would have predicted that in the mid 90s?
- jitl 6y agoThe Apple II was useless on arrival unless you could program it yourself. The iPhone is useful for 99% of customers while providing no on-device programming. Weird analogy.
- sharken 6y agoAs someone who was actually thinking about getting the M1 based on the great performance and battery life, but without any actual use for it, I can see what you mean. But the lack of openness is enough to stop those ideas, a new Surface laptop or next generation AMD mobile is much more useful. I just hope that a battery life breakthrough is on the horizon from AMD or Intel.
- api 6y agoProcess node is a large part of it. Fab a Ryzen at 5nm and it will at least be in the ballpark, though X64 decode complexity makes it hard to completely close the gap. There is also nothing stopping someone else from matching or beating M1 performance with another ARM64 core or RISC-V. Both of those have simple easy to parallelize decoders. It will be done if there is demand. AMD, Marvell, Qualcomm, and Intel all have the expertise to do it. Probably TI too if they wanted to reenter the CPU market.
- klelatti 6y agoI think you have to look beyond 'technical' ability and factor in commercial incentives: like who would be buying these CPUs and how many? Zero chance of an AMD or Intel ARM core like this in the near future. Marvell have pulled out of the Arm server market IIRC. Qualcomm a possibility but they have underwhelmed in the past. Nvidia would be my favourite post the Arm acquisition but they probably have their eye on other markets.
- selectodude 6y ago>I just hope that a battery life breakthrough is on the horizon from AMD or Intel. Intel has their Lakefield chips which use the same big.LITTLE configuration but their first large release chips will be Alder Lake next year. My concern is less with Intel and AMD's ability to implement the cores as much as Microsoft's ability to implement a scheduler. They never came to grips with the weirdness of AMD's Bulldozer architecture.
- ladyanita22 6y ago
- rgovostes 6y agoOn the other hand, Apple released their 64-bit ARM backend for LLVM[1] in 2014. They announced their intention do so almost immediately after the first ARM64 phone, but the process took several months because it had to be merged with a duplicate backend developed by others. I think it is likely that support for these instructions will be upstreamed to LLVM, and the teams involved in this monumental transition (which was announced like ~50 days ago) simply didn't put it at the highest priority on the list of things that developers need to know to get their apps working on Day 1. A fair criticism is that some of the more technical documentation, such as on the Mach-O ABI, have disappeared from Apple's developer site, or been relegated to an unsearchable archive[2], so it's very reasonable to be skeptical of ISA extensions ever being documented there. The developer site has always sucked though, and it seems to me they've declared bankruptcy and are rebuilding it on machine-generated docs and WWDC content for app developers. Occam's razor. 1: https://www.phoronix.com/scan.php?page=news_item&px=MTY0NzE https://www.phoronix.com/scan.php?page=news_item&px=MTY0NzE 2: https://developer.apple.com/library/archive/navigation/ https://developer.apple.com/library/archive/navigation/
- brigade 6y agoAMX was first announced for the A13 [1], so it's been in the wild for over a year now. 1: https://www.anandtech.com/show/14859/apple-announces-new-iphone-11-iphone-11-pro-iphone-11-pro-max https://www.anandtech.com/show/14859/apple-announces-new-iph...
- my123 6y agoAnd Apple M1 implements AMX2, not the original AMX in the A13. I'm not sure if Apple plans to ever maintain AMX compatibility across CPU versions...
- duskwuff 6y agoYou've hit on an important point here. As soon as Apple documents one of their CPU extensions, they've put themselves in the position of having to support it long-term. Leaving it undocumented gives them the freedom to make breaking changes from one CPU generation to the next -- hopefully with the end goal of deciding on an implementation and documenting the end result.
- rwmj 6y ago> Apple aren't really documenting anything for their new toys This seems an odd strategy for an accelerator. How are they expecting that people will use these new instructions? Only through Apple-supplied closed source compilers and libraries? (This is not meant to indicate you're wrong, only I'm confused about Apple's strategy)
- ac29 6y ago> How are they expecting that people will use these new instructions? Only through Apple-supplied closed source compilers and libraries? This sounds right. Forcing people to use Apple supplied and supported libraries allows Apple to make major changes in hardware without breaking compatibility (there are always edge cases, though).
- rwmj 6y agoIf the compiler generates these instructions, won't old binaries break if Apple later make changes in the hardware? (For shared libraries it would be "ok" because the old binary could use the new library, as long as Apple didn't also break the ABI).
- Someone 6y agoThe public compiler wouldn’t generate them, or only generate them when compiling with a special flag.
- egsmi 6y agoIn theory that’s what bitcode protects against. Today, that doesn’t save binaries not distributed through the store or ones you compiled yourself via other compiler chains. It is possible to change that. One could even imagine it as part of the loading procedure. https://lowlevelbits.org/bitcode-demystified/ https://lowlevelbits.org/bitcode-demystified/
- saagarjha 6y agoBitcode wouldn't really help too much here.
- EricE 6y agoOr maybe different people have different needs and don’t care if every device is “open”. The vast majority of people are not enamored with technology for technologies sake. These are tools. Does the tool do what I want with the least amount of friction? That’s what they care about. Also how does Apples stance on one product in any way change the device you are using to post in any way? Are Apple thugs coming to your house destroying non-Apple tech? Of course not! It always amuses me how Apple can simultaneously be irrelevant due to their market share and also be the greatest threat to open computing by their temerity at daring to have different computing models. If you don’t like their computing model then don’t use it. Railing that they aren’t supporting your vision lockstep is pretty freaking arrogant. Their market position is strong because they provide value that people desire. The market is not a zero sum game. Apples mere existence does diminish your computing experience. Indeed Apples existence and continually pushing computing in new areas has benefited everyone in the last 40 years - whether you use Apple or not. Just think where computing would be of the attitude that you were only a real computer user if you assembled it - at the component to board level, not just bolting pre-mad parts to a pre-made case - persisted? People criticized Apple for selling complete computers with the Apple II. Your complaint isn’t that different.
- segfaultbuserr 6y ago> If you don’t like their computing model then don’t use it. Railing that they aren’t supporting your vision lockstep is pretty freaking arrogant. Alternatively, try to learn more about it by reverse engineering, which is what this article is all about.
- mhh__ 6y ago> Or maybe different people have different needs and don’t care if every device is “open”. Just because Apple are boiling the frog doesn't make it a good thing.
- joosters 6y agoA terrible analogy, they aren't hurting anybody, something which would be fundamentally wrong. A better analogy would be that Apple is baking bread in a way that you don't like. Which is only a problem if you are forced to eat it.
- simonh 6y agoFrom an Apple perspective openness is a feature, not a goal in itself. Youre worrying about this or that specific ARM instruction, but Apple doesn't even want you to care whether it's ARM, or Intel, Or PowerPC, or whatever. It's an Apple system, part of the MacOS ecosystem and supported by Apple dev tools and power user features. If that's not the world you are interested in, what are you even doing owning a Mac? Apple does not try to be all things to all people the way e.g. Microsoft has.
- mhh__ 6y ago> If that's not the world you are interested in, what are you even doing owning a Mac? I would like consumers to have at least semblance of freedom. You have to consider that for most consumers, almost everything mentioned in this thread from top to bottom is complete Greek to the average person buying a computer. This particular question (Documenting stuff), is the cherry on top. The Sundae itself is Apple's locked-in approach to their ecosystem. The result of the Epic squabble is much more important for example, similarly I don't think it's a good thing that Apple can force Stadia to be non-native (If you were a lifelong Apple customer would you know there was any alternative?). The world is only going to get more technological - thanks to things like the cloud, the Orwells of the future will be writing about technology. As a final remark, I believe there should be broad but shallow regulation for the whole sector, Apple are just the most obvious example.
- pishpash 6y agoThat's true, at some level of abstraction you stop caring practically about openness. That line has shifted, and it points to hardware being commoditized more than lock-in. Do you care who made your logic gates or if it's documented?
- segfaultbuserr 6y ago> Do you care who made your logic gates or if it's documented? Generally no. But it's something that worth an attempt, no matter how clueless the attempt is, something positive may come out of it. Here's an attempt to implement a free and open source standard cell library using the 1-micron process from the 80s. https://github.com/chipforge/StdCellLib https://github.com/chipforge/StdCellLib
- vmception 6y agoMy life is so much better being in the Apple ecosystem. Some of it was unintentional, but now its iPhone, Macbook Pro, Apple Watch, Airpods Pro, and IOT devices that use Homekit. I have an iPad but I use it the least. Pre-Intel I used to make fun of "Apple fanboys". But aside from the niche and incompatibilities of the PowerPC architecture back then, that turned out to be a lot of other immaturities I had and was raised with. I also used to use Android, but the "look how many advanced, poorly integrated and under maintained things I can do by myself" concept didn't stay appealing for very long.
- retaeelppa 6y agoOnce you're done frolicking in the garden, tech outside can use some help. ICS and CUPS are a testament to how strange Apple is as a company. See also: libimobiledevice.org I hold that they're hands-down the worst company at marketing.
- vmception 6y agoSpeaking of the garden, what garden!? iOS devices have had a file system users can at least save and retrieve from for years now. The mobile app landscape has changed from the gold rush early last decade, and I rarely install anybody's. I empathize with the developers still trying to make it there, but its not a user's problem. The protocols that Apple chooses to promulgate work really well. Flagship games work really well. The garden has gotten really big, I can't see the walls anymore but little bad gets in. Computers do what I want them to, here. They don't do what I want them to do outside of here. For context, I jump into a Windows instance, or routinely put compute instances in the cloud.
- kelnos 6y agoIf all that works for you, that's mostly fine, and for the most part I don't think you should feel like you have to defend yourself. But two things: 1) Not all of us are like that. Admittedly I'm very far in the other camp: I run Linux as a desktop OS, and have done so for most of the past 20 years. For much of that I even ran Linux on Apple hardware (because I really did love their hardware), but a few years ago finally gave up due to the increasing frequency of undocumented things that don't work. But there are many of us (less extreme than I am, who would otherwise be content to run macOS and iOS) who absolutely do not buy in to a world where they don't truly own their devices. 2) There's a pervasive worry around here that Apple's approach will catch on, the end result being that full control over your own hardware and software will be a near impossibility. (Or, you'll be able to have it, but then be denied access to things like streaming media, and government and financial apps, a trade off people shouldn't have to make.) I think that's a very real possibility in the longer term, and I think the end result of that is total surveillance and a world where corporations decide what we're allowed to do with technology. And I think for this reason there can be a bit of hostility toward people such as yourself who are happy in the Apple walled garden and seem unconcerned about the future implications of this kind of computing model. As an aside, I also reject the idea that it's necessary that the user give up agency over their devices in order to be protected from malware. A walled garden -- no matter how far away the walls are -- is not a requirement to keep bad stuff out.
- calo_star 6y agoThis really isn't new. It looks like instead of treating the "Neural Engine" as an I/O device like the GPU, it's accessed as a coprocessor. It makes sense for them to only expose their functionalities through libraries as the underlying hardware implementation will go through changes in the future. After all, does, say, Nvidia, document their GPU's ISA?
- mhh__ 6y agoYes. Not as much as the average CPU but still documented: https://developer.nvidia.com/blog/nvidia-ampere-architecture-in-depth/ https://developer.nvidia.com/blog/nvidia-ampere-architecture...
- mhh__ 6y agohttps://github.com/NVIDIA/open-gpu-doc https://github.com/NVIDIA/open-gpu-doc Also here as well
- calo_star 6y agoWhere is the native-to-hardware ISA?
- my123 6y agoInterestingly in Nvidia's case, the CUDA Toolkit ships with nvdisasm, which is a disassembler for the native hardware ISA. They do not ship an assembler though.
- userbinator 6y agonVidia is notoriously closed, a better example would be AMD/ATI --- which do have a lot of docs on their GPUs: https://developer.amd.com/resources/developer-guides-manuals/ https://developer.amd.com/resources/developer-guides-manuals...
- zamalek 6y ago> consider that if microsoft were like this the blind eye would not be turned Microsoft was taken to court over undocumented APIs in Win 3.x that gave their own software an unfair advantage. This is why the Win32 documentation exists today.
- zepto 6y agoSure, but that’s because Microsoft had a monopoly and sold the operating system that almost everyone used. It’s worth noting that Microsoft is still in that position. Apple just isn’t.