llvm.org GIT mirror llvm / 1d6becb
fix some typos in the doc git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@292014 91177308-0d34-0410-b5e6-96231b3b80d8 Sylvestre Ledru 2 years ago
8 changed file(s) with 10 addition(s) and 10 deletion(s). Raw diff Collapse all Expand all
203203 For full list of supported instructions, refer to "SOPP Instructions" in ISA Manual.
204204
205205 Unless otherwise mentioned, little verification is performed on the operands
206 of SOPP Instrucitons, so it is up to the programmer to be familiar with the
206 of SOPP Instructions, so it is up to the programmer to be familiar with the
207207 range or acceptable values.
208208
209209 Vector ALU Instruction Examples
2020 guided optimization works is useful, but not required.
2121
2222 We start by showing how to use LLVM and Clang for code coverage analysis,
23 then we briefly desribe LLVM's code coverage mapping format and the
23 then we briefly describe LLVM's code coverage mapping format and the
2424 way that Clang and LLVM's code coverage tool work with this format. After
2525 the basics are down, more advanced features of the coverage mapping format
2626 are discussed - such as the data structures, LLVM IR representation and
737737 While this is using SVN under the hood, it does not require any interaction from
738738 you with git-svn.
739739 After a few minutes, `git pull` should get back the changes as they were
740 commited. Note that a current limitation is that `git` does not directly record
740 committed. Note that a current limitation is that `git` does not directly record
741741 file rename, and thus it is propagated to SVN as a combination of delete-add
742742 instead of a file rename.
743743
863863
864864 The ``joinErrors`` routine builds a special error type called ``ErrorList``,
865865 which holds a list of user defined errors. The ``handleErrors`` routine
866 recognizes this type and will attempt to handle each of the contained erorrs in
866 recognizes this type and will attempt to handle each of the contained errors in
867867 order. If all contained errors can be handled, ``handleErrors`` will return
868868 ``Error::success()``, otherwise ``handleErrors`` will concatenate the remaining
869869 errors and return the resulting ``ErrorList``.
2929 from SVN hosted on our own servers to Git hosted on GitHub. We are not proposing
3030 using GitHub's issue tracker, pull-requests, or code-review.
3131
32 Contributers will continue to earn commit access on demand under the Developer
32 Contributors will continue to earn commit access on demand under the Developer
3333 Policy, except that that a GitHub account will be required instead of SVN
3434 username/password-hash.
3535
432432 * Using the monolithic repository may add overhead for those *integrating* a
433433 standalone sub-project, even if they aren't contributing to it, due to the
434434 same disk space concern as the point above. The availability of the
435 sub-project Git mirror addesses this, even without SVN access.
435 sub-project Git mirror addresses this, even without SVN access.
436436 * Preservation of the existing read/write SVN-based workflows relies on the
437437 GitHub SVN bridge, which is an extra dependency. Maintaining this locks us
438438 into GitHub and could restrict future workflow changes.
312312 ret i32 0
313313 }
314314
315 ``ModuleID`` can unexpetedly match against ``CHECK`` lines. For example:
315 ``ModuleID`` can unexpectedly match against ``CHECK`` lines. For example:
316316
317317 .. code-block:: llvm
318318
592592 FPRegsClass FPRegsRegClass;
593593 IntRegsClass IntRegsRegClass;
594594 ...
595 // IntRegs Sub-register Classess...
595 // IntRegs Sub-register Classes...
596596 static const TargetRegisterClass* const IntRegsSubRegClasses [] = {
597597 NULL
598598 };
599599 ...
600 // IntRegs Super-register Classess...
600 // IntRegs Super-register Classes..
601601 static const TargetRegisterClass* const IntRegsSuperRegClasses [] = {
602602 NULL
603603 };
730730 static typing, so there are limits to how you can use tags with the YAML I/O
731731 model. Recently, we added support to YAML I/O for checking/setting the optional
732732 tag on a map. Using this functionality it is even possbile to support different
733 mappings, as long as they are convertable.
733 mappings, as long as they are convertible.
734734
735735 To check a tag, inside your mapping() method you can use io.mapTag() to specify
736736 what the tag should be. This will also add that tag when writing yaml.