Post not yet marked as solved
It's inside the SoC and this is the large cache that is shared by all the processors on an Apple Silicon chip. Why do you need to have information about this cache? It's not like you can do anything with it directly...
Post not yet marked as solved
I am also very confused by the absence of A15 in the feature tables. Note that MTLGPUFamily.apple8 (that probably refers to A15) is also undocumented. Come on, Apple, you can do better.
Regarding M1, that one shares the capabilities with A14 (same GPU), so it does not really need a separate feature entry. Would still be nice if they put in M1/A14 for clarity.
Post marked as Apple Recommended
Hardware does not support drawing thick lines and so this functionality has no business in being in a GPU API. Not to mention that there are a lot of choices that have to be done (how to handle line caps, how to handle aliasing etc.). I am surprised that some people think this is basic functionality, it clearly is not. Drawing lines either involves non-trivial shaders that interpolate SDFs or constructing geometry on the fly. This could be a task for an auxiliary library, but definitely not for the core API.
It’s now been over three months, iOS14 has been released but there is no update to the documentation... abs besides, the documentation itself is a bit, well... lacking. Come on guys, you can do better.
Post not yet marked as solved
Metal supports ray tracing as of this year. There are no new Nvidia drivers available because Nvidia and Apple don’t work together anymore. In fact, Nvidia eGPUs are not supported at all.
Post not yet marked as solved
True, and I understand that beta software can have bugs that require workarounds like this.But we are talkign about Xcode GM now. Imagine the mess if this bug is present in the official Catalina release. For instance, we have academic personell (non-programmers) who heavily rely on open-source numerical software, and its a common practice to build this from source using homebrew (to make sure that latest CPU capabilities are properly taken care of). These people wouldn't know why their software is randomly crashign and they don't understand compiler flags or how to look for solutions. All they know is how to run "brew install --build-from-source X" and they expect it to work.
Post not yet marked as solved
I have reported this issue as early as 8. August, with no reply from Apple. I am a bit alarmed that a bug as critical as this has been seemingly ignored for over a month. This essentially makes C/C++ compeltely useless for any non-trivial numerical code.
