| Index: src/assembler-ia32.h
|
| diff --git a/src/assembler-ia32.h b/src/assembler-ia32.h
|
| index 7db218ef41a671f5d312c46895f44f0f4e1541e5..cb273c0d9962d336358f32add4c20b8bbb87ef5a 100644
|
| --- a/src/assembler-ia32.h
|
| +++ b/src/assembler-ia32.h
|
| @@ -405,7 +405,7 @@ class Assembler : public Malloced {
|
|
|
| // GetCode emits any pending (non-emitted) code and fills the descriptor
|
| // desc. GetCode() is idempotent; it returns the same result if no other
|
| - // Assembler functions are invoked inbetween GetCode() calls.
|
| + // Assembler functions are invoked in between GetCode() calls.
|
| void GetCode(CodeDesc* desc);
|
|
|
| // Read/Modify the code target in the branch/call instruction at pc.
|
| @@ -430,10 +430,10 @@ class Assembler : public Malloced {
|
| // in the sense that some operations (e.g. mov()) can be called in more
|
| // the one way to generate the same instruction: The Register argument
|
| // can in some cases be replaced with an Operand(Register) argument.
|
| - // This should be cleaned up and made more othogonal. The questions
|
| + // This should be cleaned up and made more orthogonal. The questions
|
| // is: should we always use Operands instead of Registers where an
|
| // Operand is possible, or should we have a Register (overloaded) form
|
| - // instead? We must be carefull to make sure that the selected instruction
|
| + // instead? We must be careful to make sure that the selected instruction
|
| // is obvious from the parameters to avoid hard-to-find code generation
|
| // bugs.
|
|
|
|
|