Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Minor formatting fixes for the LLVM devdocs #22397

Merged
merged 1 commit into from
Jun 17, 2017
Merged

Conversation

ararslan
Copy link
Member

@ararslan ararslan commented Jun 17, 2017

In particular, there were a few places where Julia and GC should be capitalized as well as a couple of typos. I also added language annotation to the code blocks. (Highlighter supports LLVM!)

Addresses some of the things noted by @tkelman in #21888.

Note that CI has been skipped and that it should be removed from the commit message when merging to ensure the docs get built. make check-whitespace passed locally.

@ararslan ararslan added the domain:docs This change adds or pertains to documentation label Jun 17, 2017
@ararslan ararslan requested a review from Keno June 17, 2017 00:09
@ararslan
Copy link
Member Author

Btw @Keno these docs are legendary. Excellent work.

@@ -112,36 +112,36 @@ The last step is labor intensive. Suggestions on a better way would be apprecia

Julia has a generic calling convention for unoptimized code, which looks somewhat
as follows:
```
```c
jl_value_t *any_unoptimized_call(jl_value_t *, jl_value_t **, int);
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

does the indentation do any good if it's already triple-backtick-fenced?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I believe they end up showing as indented in that case. Dunno whether that was intentional.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

if it's just a single line of code, seems unnecessary?

@@ -63,29 +63,29 @@ via the environment variable `JULIA_LLVM_ARGS`. Here are example settings using
## Debugging LLVM transformations in isolation

On occasion, it can be useful to debug LLVM's transformations in isolation from
the rest of the julia system, e.g. because reproducing the issue inside julia
the rest of the Julia system, e.g. because reproducing the issue inside Julia
would take too long, or because one wants to take advantage of LLVM's tooling
(e.g. bugpoint). To get unoptimized IR for the entire system iamge, pass the
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

typo: iamge

@@ -63,29 +63,29 @@ via the environment variable `JULIA_LLVM_ARGS`. Here are example settings using
## Debugging LLVM transformations in isolation

On occasion, it can be useful to debug LLVM's transformations in isolation from
the rest of the julia system, e.g. because reproducing the issue inside julia
the rest of the Julia system, e.g. because reproducing the issue inside Julia
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

These do actually refer to the executable, so should be lower case.

image, one could do:
```
opt -load libjulia.so -julia -o opt.bc unopt.bc
llc -o sys.o opt.bc
cc -shared -o sys.so sys.o
```
This system image can then be loaded by julia as usual.
This system image can then be loaded by Julia as usual.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

also lower case here and the one above

@ararslan ararslan merged commit ae3c25b into master Jun 17, 2017
@ararslan ararslan deleted the aa/gc-root-doc-fixes branch June 17, 2017 04:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
domain:docs This change adds or pertains to documentation
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants