X-Git-Url: http://plrg.eecs.uci.edu/git/?a=blobdiff_plain;f=docs%2FExtendingLLVM.rst;h=87f48c9934257d2aaa499dfe762ca3f550f6292b;hb=79dc87fc1ed4270dcc72bf12aeb5aae9b9163041;hp=56c48af1ff35243c5b44b4497fcb3e757e53066a;hpb=79ccb55981c2219a4516f7d1ca788d988726ac2c;p=oota-llvm.git diff --git a/docs/ExtendingLLVM.rst b/docs/ExtendingLLVM.rst index 56c48af1ff3..87f48c99342 100644 --- a/docs/ExtendingLLVM.rst +++ b/docs/ExtendingLLVM.rst @@ -15,7 +15,7 @@ When you come to this realization, stop and think. Do you really need to extend LLVM? Is it a new fundamental capability that LLVM does not support at its current incarnation or can it be synthesized from already pre-existing LLVM elements? If you are not sure, ask on the `LLVM-dev -`_ list. The reason is that +`_ list. The reason is that extending LLVM will get involved as you need to update all the different passes that you intend to use with your extension, and there are ``many`` LLVM analyses and transformations, so it may be quite a bit of work. @@ -49,9 +49,9 @@ function and then be turned into an instruction if warranted. Add an entry for your intrinsic. Describe its memory access characteristics for optimization (this controls whether it will be DCE'd, CSE'd, etc). Note - that any intrinsic using the ``llvm_int_ty`` type for an argument will - be deemed by ``tblgen`` as overloaded and the corresponding suffix will - be required on the intrinsic's name. + that any intrinsic using one of the ``llvm_any*_ty`` types for an argument or + return type will be deemed by ``tblgen`` as overloaded and the corresponding + suffix will be required on the intrinsic's name. #. ``llvm/lib/Analysis/ConstantFolding.cpp``: