diff options
| author | Jonathan Roelofs <jonathan@codesourcery.com> | 2016-09-21 17:32:58 +0000 |
|---|---|---|
| committer | Jonathan Roelofs <jonathan@codesourcery.com> | 2016-09-21 17:32:58 +0000 |
| commit | 8a1434af4a307420d6af3fcf27e4d661c645f5e8 (patch) | |
| tree | 9d485e4457782b68fc1761d1951ceb69e69baffb /llvmbisect | |
| parent | 593e0d6ec97f00f854c606387bb57c59d738529f (diff) | |
Fix a couple of small spelling/grammar nits. NFC
git-svn-id: https://llvm.org/svn/llvm-project/zorg/trunk@282094 91177308-0d34-0410-b5e6-96231b3b80d8
Diffstat (limited to 'llvmbisect')
| -rw-r--r-- | llvmbisect/docs/llvmlab_bisect.rst | 8 |
1 files changed, 4 insertions, 4 deletions
diff --git a/llvmbisect/docs/llvmlab_bisect.rst b/llvmbisect/docs/llvmlab_bisect.rst index 536e7258..3ef0e38c 100644 --- a/llvmbisect/docs/llvmlab_bisect.rst +++ b/llvmbisect/docs/llvmlab_bisect.rst @@ -7,7 +7,7 @@ Automatic compiler bisecting with llvmlab bisect when a regression was introduced in any build of Clang, or LLVM produced by one of our Buildbots or Jenkins jobs. -The basics of the tool are very simple, you must provided it with a "test case" +The basics of the tool are very simple, you must provide it with a "test case" which will reproduce the problem you are seeing. Once you have done that, the tool will automatically download compiler packages from the cloud (typically produced by our continuous integration system) and will check whether @@ -78,8 +78,8 @@ are x86_64 compilers built on Yosemite in release asserts mode. Generally, you should make sure your test explicitly sets anything which could impact the test (like the architecture). -The other way this impacts your tests is that some packages are layed out -differently than others. Most compiler packages are layed out in a "Unix" style, +The other way this impacts your tests is that some packages are laid out +differently than others. Most compiler packages are laid out in a "Unix" style, with ``bin`` and ``lib`` subdirectories. One easy way to see the package layout is to use ``llvmlab fetch`` to grab a build from the particular builder you are using and poke at it. For example:: @@ -94,7 +94,7 @@ See ``llvmlab fetch --help`` for more information on the ``fetch`` tool. The main exception to remember is that Apple style builds generally will have "root" style layouts, where the package is meant to be installed directly into -``/``, and will be layed out with ``usr/bin`` and ``Developer/usr/bin`` +``/``, and will be laid out with ``usr/bin`` and ``Developer/usr/bin`` subdirectories. |