OpenHarmony/third_party_mesa3d
2
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs: remove non-existent reference

Browse Source 
The section referenced here was removed a while ago, but it was always
empty anyway. Let's just remove it instead of trying to fix it up.

Reviewed-by: Eric Engestrom <eric@engestrom.ch>
Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/5671>
This commit is contained in:
Erik Faye-Lund
2020-06-27 10:31:18 +02:00
committed by Marge Bot
parent 3b74e6fa28
commit 05e61a9157
1 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
docs/dispatch.rst
View File

@@ -219,8 +219,8 @@ implementation of each function. This makes the assembly file
considerably larger (e.g., 29,332 lines for ``glapi_x86-64.S`` versus considerably larger (e.g., 29,332 lines for ``glapi_x86-64.S`` versus
1,155 lines for ``glapi_x86.S``) and causes simple changes to the 1,155 lines for ``glapi_x86.S``) and causes simple changes to the
function implementation to generate many lines of diffs. Since the function implementation to generate many lines of diffs. Since the
assembly files are typically generated by scripts (see assembly files are typically generated by scripts, this isn't a
`below <#autogen>`__), this isn't a significant problem. significant problem.
Once a new assembly file is created, it must be inserted in the build Once a new assembly file is created, it must be inserted in the build
system. There are two steps to this. The file must first be added to system. There are two steps to this. The file must first be added to