X-Git-Url: http://plrg.eecs.uci.edu/git/?a=blobdiff_plain;f=docs%2FExtendingLLVM.html;h=647fa01d53bbca054ea108d0e1259f39f93c7d65;hb=1ac022974a75aaccc11d9f7f024044cba7ee99f8;hp=b86d561794c727f307e1a1ffaf06a113e498fa5f;hpb=099d76cf159a07d35cfb80b79c34127bf2377a0e;p=oota-llvm.git diff --git a/docs/ExtendingLLVM.html b/docs/ExtendingLLVM.html index b86d561794c..647fa01d53b 100644 --- a/docs/ExtendingLLVM.html +++ b/docs/ExtendingLLVM.html @@ -26,7 +26,8 @@
@@ -52,9 +53,9 @@ 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. -Adding an intrinsic function is easier than adding -an instruction, and is transparent to optimization passes which treat it as an -unanalyzable function. If your added functionality can be expressed as a +
Adding an intrinsic function is far easier than +adding an instruction, and is transparent to optimization passes. If your added +functionality can be expressed as a function call, an intrinsic function is the method of choice for LLVM extension.
@@ -84,28 +85,17 @@ function and then be turned into an instruction if warranted. what the restrictions are. Talk to other people about it so that you are sure it's a good idea. -WARNING: adding instructions changes the bytecode
+ WARNING: adding instructions changes the bitcode
format, and it will take some effort to maintain compatibility with
the previous version. Only add an instruction if it is absolutely
necessary.
WARNING: adding new types changes the bytecode
+ WARNING: adding new types changes the bitcode
format, and will break compatibility with currently-existing LLVM
installations. Only add new types if it is absolutely necessary.
+ src="http://jigsaw.w3.org/css-validator/images/vcss-blue" alt="Valid CSS">
+ src="http://www.w3.org/Icons/valid-html401-blue" alt="Valid HTML 4.01">
- The LLVM Compiler Infrastructure
+ The LLVM Compiler Infrastructure
Last modified: $Date$