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
{{ message }}
Repository navigation
[General]: x86-64 Assembly documentation does not describe what Jcc instructions do #89
The documentation for Jcc instructions in x86-64 Assembly is missing the information of what each cc code stands for, ie what each instruction actually does.
Add link to Condition_Holds? There's no indication of what "the preceding page" is in the sentence "The conditions for each Jcc mnemonic are given in the “Description” column of the table on the preceding page."
This needs to be fixed by modifying the master copy (i.e., the SDM PDF).
The required change is to change "preceding page" to "above" - assuming that readers of the PDF will understand that this could mean the previous page.
As we shift more focus onto the website, we are likely to run into more issues like this where
the SDM PDF is a sequence of ordered pages navigated by flipping forwards and backwards and using the table-of-contents sidebar and occasionally search (of the pages) but not the index
the website is a network of unordered pages navigated by explicit hyperlinks, multiple indexes (for instructions, helpers, categories, ...) and search (of the index)
So navigation phrases like "previous", "next", "earlier", etc. will not work for both and will have slightly different scope.
Activity
ludloff commentedon Oct 12, 2026
It is not missing.
Look for "Condition_Holds".
VaiaPatta1985 commentedon Oct 13, 2026
Add link to Condition_Holds? There's no indication of what "the preceding page" is in the sentence "The conditions for each Jcc mnemonic are given in the “Description” column of the table on the preceding page."
alastairreid commentedon Oct 21, 2026
This needs to be fixed by modifying the master copy (i.e., the SDM PDF).
The required change is to change "preceding page" to "above" - assuming that readers of the PDF will understand that this could mean the previous page.
As we shift more focus onto the website, we are likely to run into more issues like this where
So navigation phrases like "previous", "next", "earlier", etc. will not work for both and will have slightly different scope.