You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Intrinsics are very useful for optimizing certain parts of the code. But the names of the built-in functions do not give important information - what will happen to my variable. Can you improve the Intrinsics documentation for a deeper understanding - add pseudocode or graphics/visualizations of what each Intrinsic actually does?
As mentioned in 1672 I can use the Intel guide, but right now Intel has blocked access from Russia.
The text was updated successfully, but these errors were encountered:
ghost
added
untriaged
New issue has not been triaged by the area owner
needs-area-label
An area label is needed to ensure this gets routed to the appropriate area owners
labels
Jun 16, 2023
This is a legal problem. The documentation for the instructions, including the relevant psuedo-code describing how they operate, is copyrighted by the respective companies (Intel for Intel's docs, AMD for AMD's docs, etc). Due to the scale, explicit permissions are required to reproduce such documentation in our own.
There is then the additional consideration that our docs are normally creative commons, but this subset would likely not be, which adds its own complications to the process.
The current documentation does what we can and gives enough information for developers to refer to the architecture specific instruction manuals or documentation for more information on behavior.
Dear .NET developers!
Intrinsics are very useful for optimizing certain parts of the code. But the names of the built-in functions do not give important information - what will happen to my variable. Can you improve the Intrinsics documentation for a deeper understanding - add pseudocode or graphics/visualizations of what each Intrinsic actually does?
As mentioned in 1672 I can use the Intel guide, but right now Intel has blocked access from Russia.
The text was updated successfully, but these errors were encountered: