Skip to content

Commit 0baca20

Browse files
giordanoKristofferC
authored andcommitted
[docs] Fix rendering of warning admonition in llvm passes page (#56412)
Follow up to #56392: also the warning in https://docs.julialang.org/en/v1.11.1/devdocs/llvm-passes/#Multiversioning is rendered incorrectly because of a missing space. (cherry picked from commit 3de1b1d)
1 parent 515326a commit 0baca20

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

doc/src/devdocs/llvm-passes.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -98,7 +98,7 @@ This pass performs modifications to a module to create functions that are optimi
9898

9999
!!! warning
100100

101-
Use of `llvmcall` with multiversioning is dangerous. `llvmcall` enables access to features not typically exposed by the Julia APIs, and are therefore usually not available on all architectures. If multiversioning is enabled and code generation is requested for a target architecture that does not support the feature required by an `llvmcall` expression, LLVM will probably error out, likely with an abort and the message `LLVM ERROR: Do not know how to split the result of this operator!`.
101+
Use of `llvmcall` with multiversioning is dangerous. `llvmcall` enables access to features not typically exposed by the Julia APIs, and are therefore usually not available on all architectures. If multiversioning is enabled and code generation is requested for a target architecture that does not support the feature required by an `llvmcall` expression, LLVM will probably error out, likely with an abort and the message `LLVM ERROR: Do not know how to split the result of this operator!`.
102102

103103
### GCInvariantVerifier
104104

0 commit comments

Comments
 (0)