Skip to content

Commit

Permalink
Merge pull request #10584 from garrison/more-typos
Browse files Browse the repository at this point in the history
Fix more typos in documentation
  • Loading branch information
jakebolewski committed Mar 20, 2015
2 parents 7f47a11 + 7d71bf5 commit b43f0b0
Show file tree
Hide file tree
Showing 2 changed files with 4 additions and 4 deletions.
6 changes: 3 additions & 3 deletions doc/devdocs/eval.rst
Original file line number Diff line number Diff line change
Expand Up @@ -91,7 +91,7 @@ Type Inference
Type inference is implemented in Julia by `typeinf() in inference.jl <https://github.com/JuliaLang/julia/blob/master/base/inference.jl>`_.
Type inference is the process of examining a Julia function and determining bounds for the types of each of its variables,
as well as bounds on the type of the return value from the function.
This enables may future optimizations, such as unboxing of known immutable values,
This enables many future optimizations, such as unboxing of known immutable values,
and compile-time hoisting of various run-time operations such as computing field offsets and function pointers.
Type inference may also include other steps such as constant propagation and inlining.

Expand Down Expand Up @@ -140,7 +140,7 @@ JIT Code Generation
A low-level operation exposed as a function in Julia.
These pseudo-functions implement operations on raw bits such as add and sign extend
that cannot be expressed directly in any other way.
Since the operate on bits directly, they must be compiled into a function
Since they operate on bits directly, they must be compiled into a function
and surrounded by a call to `Core.Intrinsics.box(T, ...)` to reassign type information to the value.

Codegen is the process of turning a Julia AST into native machine code.
Expand Down Expand Up @@ -184,7 +184,7 @@ The `sys.ji` file distributed with Julia is one such system image,
generated by executing the file `sysimg.jl <https://github.com/JuliaLang/julia/blob/master/base/sysimg.jl>`_,
and serializing the resulting environment (including Types, Functions, Modules, and all other defined values)
into a file. Therefore, it contains a frozen version of the "Main", "Core", and "Base" modules (and whatever else was in the environment at the end of bootstrapping).
This serializer/deserializer is implemented by `jl_save_system_image/jl_restore_system_image in dump.c <https://github.com/JuliaLang/julia/blob/master/src/dump.c>`
This serializer/deserializer is implemented by `jl_save_system_image/jl_restore_system_image in dump.c <https://github.com/JuliaLang/julia/blob/master/src/dump.c>`_.

If there is no sysimg file (:code:`jl_compileropts.image_file == NULL`),
this also implies that `--build` was given on the command line,
Expand Down
2 changes: 1 addition & 1 deletion doc/devdocs/init.rst
Original file line number Diff line number Diff line change
Expand Up @@ -22,7 +22,7 @@ Next `parse_opts()
is called to process command line options. Note that parse_opts()
only deals with options that affect code generation or early initialisation. Other
options are handled later by `process_options() in base/client.jl
<https://github.com/JuliaLang/julia/blob/master/base/client.jl#L214>`_
<https://github.com/JuliaLang/julia/blob/master/base/client.jl#L214>`_.

parse_opts() stores command line options in the `global jl_compileropts
struct
Expand Down

0 comments on commit b43f0b0

Please sign in to comment.