From e2c3a49c8029ebd9ef530101cc24c66562e3dff5 Mon Sep 17 00:00:00 2001 From: mike-m Date: Fri, 7 May 2010 00:28:04 +0000 Subject: Revert r103213. It broke several sections of live website. git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@103219 91177308-0d34-0410-b5e6-96231b3b80d8 --- docs/AliasAnalysis.html | 937 +++ docs/BitCodeFormat.html | 1163 +++ docs/Bugpoint.html | 250 + docs/CFEBuildInstrs.html | 29 + docs/CMake.html | 384 + docs/CodeGenerator.html | 2169 ++++++ docs/CodingStandards.html | 1353 ++++ docs/CommandGuide/FileCheck.pod | 245 + docs/CommandGuide/Makefile | 103 + docs/CommandGuide/bugpoint.pod | 167 + docs/CommandGuide/html/manpage.css | 256 + docs/CommandGuide/index.html | 155 + docs/CommandGuide/lit.pod | 354 + docs/CommandGuide/llc.pod | 193 + docs/CommandGuide/lli.pod | 216 + docs/CommandGuide/llvm-ar.pod | 406 + docs/CommandGuide/llvm-as.pod | 77 + docs/CommandGuide/llvm-bcanalyzer.pod | 315 + docs/CommandGuide/llvm-config.pod | 131 + docs/CommandGuide/llvm-dis.pod | 60 + docs/CommandGuide/llvm-extract.pod | 73 + docs/CommandGuide/llvm-ld.pod | 234 + docs/CommandGuide/llvm-link.pod | 79 + docs/CommandGuide/llvm-nm.pod | 122 + docs/CommandGuide/llvm-prof.pod | 57 + docs/CommandGuide/llvm-ranlib.pod | 52 + docs/CommandGuide/llvmc.pod | 190 + docs/CommandGuide/llvmgcc.pod | 76 + docs/CommandGuide/llvmgxx.pod | 85 + docs/CommandGuide/manpage.css | 256 + docs/CommandGuide/opt.pod | 143 + docs/CommandGuide/tblgen.pod | 115 + docs/CommandLine.html | 1979 +++++ docs/CompilerDriver.html | 756 ++ docs/CompilerDriverTutorial.html | 126 + docs/CompilerWriterInfo.html | 263 + docs/DebuggingJITedCode.html | 171 + docs/DeveloperPolicy.html | 607 ++ docs/ExceptionHandling.html | 606 ++ docs/ExtendedIntegerResults.txt | 133 + docs/ExtendingLLVM.html | 391 + docs/FAQ.html | 938 +++ docs/GCCFEBuildInstrs.html | 279 + docs/GarbageCollection.html | 1387 ++++ docs/GetElementPtr.html | 734 ++ docs/GettingStarted.html | 1679 +++++ docs/GettingStartedVS.html | 417 ++ docs/GoldPlugin.html | 213 + .../2000-11-18-EarlyDesignIdeas.txt | 74 + .../2000-11-18-EarlyDesignIdeasResp.txt | 199 + docs/HistoricalNotes/2000-12-06-EncodingIdea.txt | 30 + docs/HistoricalNotes/2000-12-06-MeetingSummary.txt | 83 + .../HistoricalNotes/2001-01-31-UniversalIRIdea.txt | 39 + .../2001-02-06-TypeNotationDebate.txt | 67 + .../2001-02-06-TypeNotationDebateResp1.txt | 75 + .../2001-02-06-TypeNotationDebateResp2.txt | 53 + .../2001-02-06-TypeNotationDebateResp4.txt | 89 + docs/HistoricalNotes/2001-02-09-AdveComments.txt | 120 + .../2001-02-09-AdveCommentsResponse.txt | 245 + .../2001-02-13-Reference-Memory.txt | 39 + .../2001-02-13-Reference-MemoryResponse.txt | 47 + .../2001-04-16-DynamicCompilation.txt | 49 + .../2001-05-18-ExceptionHandling.txt | 202 + .../2001-05-19-ExceptionResponse.txt | 45 + .../2001-06-01-GCCOptimizations.txt | 63 + .../2001-06-01-GCCOptimizations2.txt | 71 + .../2001-06-20-.NET-Differences.txt | 30 + .../2001-07-06-LoweringIRForCodeGen.txt | 31 + .../2001-09-18-OptimizeExceptions.txt | 56 + docs/HistoricalNotes/2002-05-12-InstListChange.txt | 55 + docs/HistoricalNotes/2002-06-25-MegaPatchInfo.txt | 72 + docs/HistoricalNotes/2003-01-23-CygwinNotes.txt | 28 + docs/HistoricalNotes/2003-06-25-Reoptimizer1.txt | 137 + docs/HistoricalNotes/2003-06-26-Reoptimizer2.txt | 110 + docs/HistoricalNotes/2007-OriginalClangReadme.txt | 178 + docs/HowToReleaseLLVM.html | 523 ++ docs/HowToSubmitABug.html | 347 + docs/LangRef.html | 7780 ++++++++++++++++++++ docs/Lexicon.html | 277 + docs/LinkTimeOptimization.html | 390 + docs/Makefile | 114 +- docs/MakefileGuide.html | 1031 +++ docs/Packaging.html | 118 + docs/Passes.html | 1770 +++++ docs/ProgrammersManual.html | 3950 ++++++++++ docs/Projects.html | 460 ++ docs/ReleaseNotes.html | 1237 ++++ docs/SourceLevelDebugging.html | 1780 +++++ docs/SystemLibrary.html | 319 + docs/TableGenFundamentals.html | 802 ++ docs/TestingGuide.html | 1212 +++ docs/UsingLibraries.html | 439 ++ docs/WritingAnLLVMBackend.html | 2561 +++++++ docs/WritingAnLLVMPass.html | 1842 +++++ docs/api/Makefile | 25 - docs/api/api.css | 319 - docs/api/doxygen.cfg.in | 1553 ---- docs/api/footer.html | 14 - docs/api/header.html | 13 - docs/api/intro.h | 26 - docs/api/layout.xml | 184 - docs/doxygen.cfg.in | 1419 ++++ docs/doxygen.css | 378 + docs/doxygen.footer | 13 + docs/doxygen.header | 9 + docs/doxygen.intro | 18 + docs/img/Debugging.gif | Bin 0 -> 20390 bytes docs/img/libdeps.gif | Bin 0 -> 52679 bytes docs/img/lines.gif | Bin 0 -> 91 bytes docs/img/objdeps.gif | Bin 0 -> 16201 bytes docs/img/venusflytrap.jpg | Bin 0 -> 56606 bytes docs/index.html | 293 + docs/llvm.css | 100 + docs/main/AliasAnalysis.html | 937 --- docs/main/BitCodeFormat.html | 1163 --- docs/main/Bugpoint.html | 250 - docs/main/CFEBuildInstrs.html | 29 - docs/main/CMake.html | 384 - docs/main/CodeGenerator.html | 2169 ------ docs/main/CodingStandards.html | 1353 ---- docs/main/CommandGuide/FileCheck.pod | 245 - docs/main/CommandGuide/bugpoint.pod | 167 - docs/main/CommandGuide/index.html | 155 - docs/main/CommandGuide/lit.pod | 354 - docs/main/CommandGuide/llc.pod | 193 - docs/main/CommandGuide/lli.pod | 216 - docs/main/CommandGuide/llvm-ar.pod | 406 - docs/main/CommandGuide/llvm-as.pod | 77 - docs/main/CommandGuide/llvm-bcanalyzer.pod | 315 - docs/main/CommandGuide/llvm-config.pod | 131 - docs/main/CommandGuide/llvm-dis.pod | 60 - docs/main/CommandGuide/llvm-extract.pod | 73 - docs/main/CommandGuide/llvm-ld.pod | 234 - docs/main/CommandGuide/llvm-link.pod | 79 - docs/main/CommandGuide/llvm-nm.pod | 122 - docs/main/CommandGuide/llvm-prof.pod | 57 - docs/main/CommandGuide/llvm-ranlib.pod | 52 - docs/main/CommandGuide/llvmc.pod | 190 - docs/main/CommandGuide/llvmgcc.pod | 76 - docs/main/CommandGuide/llvmgxx.pod | 85 - docs/main/CommandGuide/manpage.css | 256 - docs/main/CommandGuide/opt.pod | 143 - docs/main/CommandGuide/tblgen.pod | 115 - docs/main/CommandLine.html | 1979 ----- docs/main/CompilerDriver.html | 756 -- docs/main/CompilerDriverTutorial.html | 126 - docs/main/CompilerWriterInfo.html | 263 - docs/main/DebuggingJITedCode.html | 171 - docs/main/DeveloperPolicy.html | 607 -- docs/main/ExceptionHandling.html | 606 -- docs/main/ExtendedIntegerResults.txt | 133 - docs/main/ExtendingLLVM.html | 391 - docs/main/FAQ.html | 938 --- docs/main/GCCFEBuildInstrs.html | 279 - docs/main/GarbageCollection.html | 1387 ---- docs/main/GetElementPtr.html | 734 -- docs/main/GettingStarted.html | 1679 ----- docs/main/GettingStartedVS.html | 417 -- docs/main/GoldPlugin.html | 213 - .../2000-11-18-EarlyDesignIdeas.txt | 74 - .../2000-11-18-EarlyDesignIdeasResp.txt | 199 - .../HistoricalNotes/2000-12-06-EncodingIdea.txt | 30 - .../HistoricalNotes/2000-12-06-MeetingSummary.txt | 83 - .../HistoricalNotes/2001-01-31-UniversalIRIdea.txt | 39 - .../2001-02-06-TypeNotationDebate.txt | 67 - .../2001-02-06-TypeNotationDebateResp1.txt | 75 - .../2001-02-06-TypeNotationDebateResp2.txt | 53 - .../2001-02-06-TypeNotationDebateResp4.txt | 89 - .../HistoricalNotes/2001-02-09-AdveComments.txt | 120 - .../2001-02-09-AdveCommentsResponse.txt | 245 - .../2001-02-13-Reference-Memory.txt | 39 - .../2001-02-13-Reference-MemoryResponse.txt | 47 - .../2001-04-16-DynamicCompilation.txt | 49 - .../2001-05-18-ExceptionHandling.txt | 202 - .../2001-05-19-ExceptionResponse.txt | 45 - .../2001-06-01-GCCOptimizations.txt | 63 - .../2001-06-01-GCCOptimizations2.txt | 71 - .../2001-06-20-.NET-Differences.txt | 30 - .../2001-07-06-LoweringIRForCodeGen.txt | 31 - .../2001-09-18-OptimizeExceptions.txt | 56 - .../HistoricalNotes/2002-05-12-InstListChange.txt | 55 - .../HistoricalNotes/2002-06-25-MegaPatchInfo.txt | 72 - .../HistoricalNotes/2003-01-23-CygwinNotes.txt | 28 - .../HistoricalNotes/2003-06-25-Reoptimizer1.txt | 137 - .../HistoricalNotes/2003-06-26-Reoptimizer2.txt | 110 - .../HistoricalNotes/2007-OriginalClangReadme.txt | 178 - docs/main/HowToReleaseLLVM.html | 523 -- docs/main/HowToSubmitABug.html | 347 - docs/main/LangRef.html | 7780 -------------------- docs/main/Lexicon.html | 277 - docs/main/LinkTimeOptimization.html | 390 - docs/main/Makefile | 18 - docs/main/MakefileGuide.html | 1031 --- docs/main/Packaging.html | 118 - docs/main/Passes.html | 1770 ----- docs/main/ProgrammersManual.html | 3950 ---------- docs/main/Projects.html | 460 -- docs/main/ReleaseNotes.html | 1237 ---- docs/main/SourceLevelDebugging.html | 1780 ----- docs/main/SystemLibrary.html | 319 - docs/main/TableGenFundamentals.html | 802 -- docs/main/TestingGuide.html | 1212 --- docs/main/UsingLibraries.html | 439 -- docs/main/WritingAnLLVMBackend.html | 2561 ------- docs/main/WritingAnLLVMPass.html | 1842 ----- docs/main/img/Debugging.gif | Bin 20390 -> 0 bytes docs/main/img/libdeps.gif | Bin 52679 -> 0 bytes docs/main/img/lines.gif | Bin 91 -> 0 bytes docs/main/img/objdeps.gif | Bin 16201 -> 0 bytes docs/main/img/venusflytrap.jpg | Bin 56606 -> 0 bytes docs/main/index.html | 293 - docs/main/llvm.css | 100 - docs/main/re_format.7 | 756 -- docs/main/tutorial/LangImpl1.html | 348 - docs/main/tutorial/LangImpl2.html | 1233 ---- docs/main/tutorial/LangImpl3.html | 1269 ---- docs/main/tutorial/LangImpl4.html | 1132 --- docs/main/tutorial/LangImpl5-cfg.png | Bin 38586 -> 0 bytes docs/main/tutorial/LangImpl5.html | 1777 ----- docs/main/tutorial/LangImpl6.html | 1814 ----- docs/main/tutorial/LangImpl7.html | 2164 ------ docs/main/tutorial/LangImpl8.html | 365 - docs/main/tutorial/OCamlLangImpl1.html | 365 - docs/main/tutorial/OCamlLangImpl2.html | 1045 --- docs/main/tutorial/OCamlLangImpl3.html | 1093 --- docs/main/tutorial/OCamlLangImpl4.html | 1029 --- docs/main/tutorial/OCamlLangImpl5.html | 1569 ---- docs/main/tutorial/OCamlLangImpl6.html | 1574 ---- docs/main/tutorial/OCamlLangImpl7.html | 1907 ----- docs/main/tutorial/index.html | 48 - docs/mk/api.mk | 205 - docs/mk/common.defs.mk | 119 - docs/mk/common.rules.mk | 54 - docs/mk/main.mk | 243 - docs/re_format.7 | 756 ++ docs/tutorial/LangImpl1.html | 348 + docs/tutorial/LangImpl2.html | 1233 ++++ docs/tutorial/LangImpl3.html | 1269 ++++ docs/tutorial/LangImpl4.html | 1132 +++ docs/tutorial/LangImpl5-cfg.png | Bin 0 -> 38586 bytes docs/tutorial/LangImpl5.html | 1777 +++++ docs/tutorial/LangImpl6.html | 1814 +++++ docs/tutorial/LangImpl7.html | 2164 ++++++ docs/tutorial/LangImpl8.html | 365 + docs/tutorial/Makefile | 28 + docs/tutorial/OCamlLangImpl1.html | 365 + docs/tutorial/OCamlLangImpl2.html | 1045 +++ docs/tutorial/OCamlLangImpl3.html | 1093 +++ docs/tutorial/OCamlLangImpl4.html | 1029 +++ docs/tutorial/OCamlLangImpl5.html | 1569 ++++ docs/tutorial/OCamlLangImpl6.html | 1574 ++++ docs/tutorial/OCamlLangImpl7.html | 1907 +++++ docs/tutorial/index.html | 48 + 253 files changed, 72107 insertions(+), 72546 deletions(-) create mode 100644 docs/AliasAnalysis.html create mode 100644 docs/BitCodeFormat.html create mode 100644 docs/Bugpoint.html create mode 100644 docs/CFEBuildInstrs.html create mode 100644 docs/CMake.html create mode 100644 docs/CodeGenerator.html create mode 100644 docs/CodingStandards.html create mode 100644 docs/CommandGuide/FileCheck.pod create mode 100644 docs/CommandGuide/Makefile create mode 100644 docs/CommandGuide/bugpoint.pod create mode 100644 docs/CommandGuide/html/manpage.css create mode 100644 docs/CommandGuide/index.html create mode 100644 docs/CommandGuide/lit.pod create mode 100644 docs/CommandGuide/llc.pod create mode 100644 docs/CommandGuide/lli.pod create mode 100644 docs/CommandGuide/llvm-ar.pod create mode 100644 docs/CommandGuide/llvm-as.pod create mode 100644 docs/CommandGuide/llvm-bcanalyzer.pod create mode 100644 docs/CommandGuide/llvm-config.pod create mode 100644 docs/CommandGuide/llvm-dis.pod create mode 100644 docs/CommandGuide/llvm-extract.pod create mode 100644 docs/CommandGuide/llvm-ld.pod create mode 100644 docs/CommandGuide/llvm-link.pod create mode 100644 docs/CommandGuide/llvm-nm.pod create mode 100644 docs/CommandGuide/llvm-prof.pod create mode 100644 docs/CommandGuide/llvm-ranlib.pod create mode 100644 docs/CommandGuide/llvmc.pod create mode 100644 docs/CommandGuide/llvmgcc.pod create mode 100644 docs/CommandGuide/llvmgxx.pod create mode 100644 docs/CommandGuide/manpage.css create mode 100644 docs/CommandGuide/opt.pod create mode 100644 docs/CommandGuide/tblgen.pod create mode 100644 docs/CommandLine.html create mode 100644 docs/CompilerDriver.html create mode 100644 docs/CompilerDriverTutorial.html create mode 100644 docs/CompilerWriterInfo.html create mode 100644 docs/DebuggingJITedCode.html create mode 100644 docs/DeveloperPolicy.html create mode 100644 docs/ExceptionHandling.html create mode 100644 docs/ExtendedIntegerResults.txt create mode 100644 docs/ExtendingLLVM.html create mode 100644 docs/FAQ.html create mode 100644 docs/GCCFEBuildInstrs.html create mode 100644 docs/GarbageCollection.html create mode 100644 docs/GetElementPtr.html create mode 100644 docs/GettingStarted.html create mode 100644 docs/GettingStartedVS.html create mode 100644 docs/GoldPlugin.html create mode 100644 docs/HistoricalNotes/2000-11-18-EarlyDesignIdeas.txt create mode 100644 docs/HistoricalNotes/2000-11-18-EarlyDesignIdeasResp.txt create mode 100644 docs/HistoricalNotes/2000-12-06-EncodingIdea.txt create mode 100644 docs/HistoricalNotes/2000-12-06-MeetingSummary.txt create mode 100644 docs/HistoricalNotes/2001-01-31-UniversalIRIdea.txt create mode 100644 docs/HistoricalNotes/2001-02-06-TypeNotationDebate.txt create mode 100644 docs/HistoricalNotes/2001-02-06-TypeNotationDebateResp1.txt create mode 100644 docs/HistoricalNotes/2001-02-06-TypeNotationDebateResp2.txt create mode 100644 docs/HistoricalNotes/2001-02-06-TypeNotationDebateResp4.txt create mode 100644 docs/HistoricalNotes/2001-02-09-AdveComments.txt create mode 100644 docs/HistoricalNotes/2001-02-09-AdveCommentsResponse.txt create mode 100644 docs/HistoricalNotes/2001-02-13-Reference-Memory.txt create mode 100644 docs/HistoricalNotes/2001-02-13-Reference-MemoryResponse.txt create mode 100644 docs/HistoricalNotes/2001-04-16-DynamicCompilation.txt create mode 100644 docs/HistoricalNotes/2001-05-18-ExceptionHandling.txt create mode 100644 docs/HistoricalNotes/2001-05-19-ExceptionResponse.txt create mode 100644 docs/HistoricalNotes/2001-06-01-GCCOptimizations.txt create mode 100644 docs/HistoricalNotes/2001-06-01-GCCOptimizations2.txt create mode 100644 docs/HistoricalNotes/2001-06-20-.NET-Differences.txt create mode 100644 docs/HistoricalNotes/2001-07-06-LoweringIRForCodeGen.txt create mode 100644 docs/HistoricalNotes/2001-09-18-OptimizeExceptions.txt create mode 100644 docs/HistoricalNotes/2002-05-12-InstListChange.txt create mode 100644 docs/HistoricalNotes/2002-06-25-MegaPatchInfo.txt create mode 100644 docs/HistoricalNotes/2003-01-23-CygwinNotes.txt create mode 100644 docs/HistoricalNotes/2003-06-25-Reoptimizer1.txt create mode 100644 docs/HistoricalNotes/2003-06-26-Reoptimizer2.txt create mode 100644 docs/HistoricalNotes/2007-OriginalClangReadme.txt create mode 100644 docs/HowToReleaseLLVM.html create mode 100644 docs/HowToSubmitABug.html create mode 100644 docs/LangRef.html create mode 100644 docs/Lexicon.html create mode 100644 docs/LinkTimeOptimization.html create mode 100644 docs/MakefileGuide.html create mode 100644 docs/Packaging.html create mode 100644 docs/Passes.html create mode 100644 docs/ProgrammersManual.html create mode 100644 docs/Projects.html create mode 100644 docs/ReleaseNotes.html create mode 100644 docs/SourceLevelDebugging.html create mode 100644 docs/SystemLibrary.html create mode 100644 docs/TableGenFundamentals.html create mode 100644 docs/TestingGuide.html create mode 100644 docs/UsingLibraries.html create mode 100644 docs/WritingAnLLVMBackend.html create mode 100644 docs/WritingAnLLVMPass.html delete mode 100644 docs/api/Makefile delete mode 100644 docs/api/api.css delete mode 100644 docs/api/doxygen.cfg.in delete mode 100644 docs/api/footer.html delete mode 100644 docs/api/header.html delete mode 100644 docs/api/intro.h delete mode 100644 docs/api/layout.xml create mode 100644 docs/doxygen.cfg.in create mode 100644 docs/doxygen.css create mode 100644 docs/doxygen.footer create mode 100644 docs/doxygen.header create mode 100644 docs/doxygen.intro create mode 100644 docs/img/Debugging.gif create mode 100644 docs/img/libdeps.gif create mode 100644 docs/img/lines.gif create mode 100644 docs/img/objdeps.gif create mode 100644 docs/img/venusflytrap.jpg create mode 100644 docs/index.html create mode 100644 docs/llvm.css delete mode 100644 docs/main/AliasAnalysis.html delete mode 100644 docs/main/BitCodeFormat.html delete mode 100644 docs/main/Bugpoint.html delete mode 100644 docs/main/CFEBuildInstrs.html delete mode 100644 docs/main/CMake.html delete mode 100644 docs/main/CodeGenerator.html delete mode 100644 docs/main/CodingStandards.html delete mode 100644 docs/main/CommandGuide/FileCheck.pod delete mode 100644 docs/main/CommandGuide/bugpoint.pod delete mode 100644 docs/main/CommandGuide/index.html delete mode 100644 docs/main/CommandGuide/lit.pod delete mode 100644 docs/main/CommandGuide/llc.pod delete mode 100644 docs/main/CommandGuide/lli.pod delete mode 100644 docs/main/CommandGuide/llvm-ar.pod delete mode 100644 docs/main/CommandGuide/llvm-as.pod delete mode 100644 docs/main/CommandGuide/llvm-bcanalyzer.pod delete mode 100644 docs/main/CommandGuide/llvm-config.pod delete mode 100644 docs/main/CommandGuide/llvm-dis.pod delete mode 100644 docs/main/CommandGuide/llvm-extract.pod delete mode 100644 docs/main/CommandGuide/llvm-ld.pod delete mode 100644 docs/main/CommandGuide/llvm-link.pod delete mode 100644 docs/main/CommandGuide/llvm-nm.pod delete mode 100644 docs/main/CommandGuide/llvm-prof.pod delete mode 100644 docs/main/CommandGuide/llvm-ranlib.pod delete mode 100644 docs/main/CommandGuide/llvmc.pod delete mode 100644 docs/main/CommandGuide/llvmgcc.pod delete mode 100644 docs/main/CommandGuide/llvmgxx.pod delete mode 100644 docs/main/CommandGuide/manpage.css delete mode 100644 docs/main/CommandGuide/opt.pod delete mode 100644 docs/main/CommandGuide/tblgen.pod delete mode 100644 docs/main/CommandLine.html delete mode 100644 docs/main/CompilerDriver.html delete mode 100644 docs/main/CompilerDriverTutorial.html delete mode 100644 docs/main/CompilerWriterInfo.html delete mode 100644 docs/main/DebuggingJITedCode.html delete mode 100644 docs/main/DeveloperPolicy.html delete mode 100644 docs/main/ExceptionHandling.html delete mode 100644 docs/main/ExtendedIntegerResults.txt delete mode 100644 docs/main/ExtendingLLVM.html delete mode 100644 docs/main/FAQ.html delete mode 100644 docs/main/GCCFEBuildInstrs.html delete mode 100644 docs/main/GarbageCollection.html delete mode 100644 docs/main/GetElementPtr.html delete mode 100644 docs/main/GettingStarted.html delete mode 100644 docs/main/GettingStartedVS.html delete mode 100644 docs/main/GoldPlugin.html delete mode 100644 docs/main/HistoricalNotes/2000-11-18-EarlyDesignIdeas.txt delete mode 100644 docs/main/HistoricalNotes/2000-11-18-EarlyDesignIdeasResp.txt delete mode 100644 docs/main/HistoricalNotes/2000-12-06-EncodingIdea.txt delete mode 100644 docs/main/HistoricalNotes/2000-12-06-MeetingSummary.txt delete mode 100644 docs/main/HistoricalNotes/2001-01-31-UniversalIRIdea.txt delete mode 100644 docs/main/HistoricalNotes/2001-02-06-TypeNotationDebate.txt delete mode 100644 docs/main/HistoricalNotes/2001-02-06-TypeNotationDebateResp1.txt delete mode 100644 docs/main/HistoricalNotes/2001-02-06-TypeNotationDebateResp2.txt delete mode 100644 docs/main/HistoricalNotes/2001-02-06-TypeNotationDebateResp4.txt delete mode 100644 docs/main/HistoricalNotes/2001-02-09-AdveComments.txt delete mode 100644 docs/main/HistoricalNotes/2001-02-09-AdveCommentsResponse.txt delete mode 100644 docs/main/HistoricalNotes/2001-02-13-Reference-Memory.txt delete mode 100644 docs/main/HistoricalNotes/2001-02-13-Reference-MemoryResponse.txt delete mode 100644 docs/main/HistoricalNotes/2001-04-16-DynamicCompilation.txt delete mode 100644 docs/main/HistoricalNotes/2001-05-18-ExceptionHandling.txt delete mode 100644 docs/main/HistoricalNotes/2001-05-19-ExceptionResponse.txt delete mode 100644 docs/main/HistoricalNotes/2001-06-01-GCCOptimizations.txt delete mode 100644 docs/main/HistoricalNotes/2001-06-01-GCCOptimizations2.txt delete mode 100644 docs/main/HistoricalNotes/2001-06-20-.NET-Differences.txt delete mode 100644 docs/main/HistoricalNotes/2001-07-06-LoweringIRForCodeGen.txt delete mode 100644 docs/main/HistoricalNotes/2001-09-18-OptimizeExceptions.txt delete mode 100644 docs/main/HistoricalNotes/2002-05-12-InstListChange.txt delete mode 100644 docs/main/HistoricalNotes/2002-06-25-MegaPatchInfo.txt delete mode 100644 docs/main/HistoricalNotes/2003-01-23-CygwinNotes.txt delete mode 100644 docs/main/HistoricalNotes/2003-06-25-Reoptimizer1.txt delete mode 100644 docs/main/HistoricalNotes/2003-06-26-Reoptimizer2.txt delete mode 100644 docs/main/HistoricalNotes/2007-OriginalClangReadme.txt delete mode 100644 docs/main/HowToReleaseLLVM.html delete mode 100644 docs/main/HowToSubmitABug.html delete mode 100644 docs/main/LangRef.html delete mode 100644 docs/main/Lexicon.html delete mode 100644 docs/main/LinkTimeOptimization.html delete mode 100644 docs/main/Makefile delete mode 100644 docs/main/MakefileGuide.html delete mode 100644 docs/main/Packaging.html delete mode 100644 docs/main/Passes.html delete mode 100644 docs/main/ProgrammersManual.html delete mode 100644 docs/main/Projects.html delete mode 100644 docs/main/ReleaseNotes.html delete mode 100644 docs/main/SourceLevelDebugging.html delete mode 100644 docs/main/SystemLibrary.html delete mode 100644 docs/main/TableGenFundamentals.html delete mode 100644 docs/main/TestingGuide.html delete mode 100644 docs/main/UsingLibraries.html delete mode 100644 docs/main/WritingAnLLVMBackend.html delete mode 100644 docs/main/WritingAnLLVMPass.html delete mode 100644 docs/main/img/Debugging.gif delete mode 100644 docs/main/img/libdeps.gif delete mode 100644 docs/main/img/lines.gif delete mode 100644 docs/main/img/objdeps.gif delete mode 100644 docs/main/img/venusflytrap.jpg delete mode 100644 docs/main/index.html delete mode 100644 docs/main/llvm.css delete mode 100644 docs/main/re_format.7 delete mode 100644 docs/main/tutorial/LangImpl1.html delete mode 100644 docs/main/tutorial/LangImpl2.html delete mode 100644 docs/main/tutorial/LangImpl3.html delete mode 100644 docs/main/tutorial/LangImpl4.html delete mode 100644 docs/main/tutorial/LangImpl5-cfg.png delete mode 100644 docs/main/tutorial/LangImpl5.html delete mode 100644 docs/main/tutorial/LangImpl6.html delete mode 100644 docs/main/tutorial/LangImpl7.html delete mode 100644 docs/main/tutorial/LangImpl8.html delete mode 100644 docs/main/tutorial/OCamlLangImpl1.html delete mode 100644 docs/main/tutorial/OCamlLangImpl2.html delete mode 100644 docs/main/tutorial/OCamlLangImpl3.html delete mode 100644 docs/main/tutorial/OCamlLangImpl4.html delete mode 100644 docs/main/tutorial/OCamlLangImpl5.html delete mode 100644 docs/main/tutorial/OCamlLangImpl6.html delete mode 100644 docs/main/tutorial/OCamlLangImpl7.html delete mode 100644 docs/main/tutorial/index.html delete mode 100644 docs/mk/api.mk delete mode 100644 docs/mk/common.defs.mk delete mode 100644 docs/mk/common.rules.mk delete mode 100644 docs/mk/main.mk create mode 100644 docs/re_format.7 create mode 100644 docs/tutorial/LangImpl1.html create mode 100644 docs/tutorial/LangImpl2.html create mode 100644 docs/tutorial/LangImpl3.html create mode 100644 docs/tutorial/LangImpl4.html create mode 100644 docs/tutorial/LangImpl5-cfg.png create mode 100644 docs/tutorial/LangImpl5.html create mode 100644 docs/tutorial/LangImpl6.html create mode 100644 docs/tutorial/LangImpl7.html create mode 100644 docs/tutorial/LangImpl8.html create mode 100644 docs/tutorial/Makefile create mode 100644 docs/tutorial/OCamlLangImpl1.html create mode 100644 docs/tutorial/OCamlLangImpl2.html create mode 100644 docs/tutorial/OCamlLangImpl3.html create mode 100644 docs/tutorial/OCamlLangImpl4.html create mode 100644 docs/tutorial/OCamlLangImpl5.html create mode 100644 docs/tutorial/OCamlLangImpl6.html create mode 100644 docs/tutorial/OCamlLangImpl7.html create mode 100644 docs/tutorial/index.html diff --git a/docs/AliasAnalysis.html b/docs/AliasAnalysis.html new file mode 100644 index 0000000000..5b4eb937a5 --- /dev/null +++ b/docs/AliasAnalysis.html @@ -0,0 +1,937 @@ + + + + LLVM Alias Analysis Infrastructure + + + + +
+ LLVM Alias Analysis Infrastructure +
+ +
    +
  1. Introduction
    2. + +
  2. AliasAnalysis Class Overview + +
    3. + +
  3. Writing a new AliasAnalysis Implementation + +
    4. + +
  4. Using alias analysis results + +
    5. + +
  5. Existing alias analysis implementations and clients + +
    6. +
  6. Memory Dependence Analysis
    7. +
+ +
+

Written by Chris Lattner

+
+ + +
+ Introduction +
+ + +
+ +

Alias Analysis (aka Pointer Analysis) is a class of techniques which attempt +to determine whether or not two pointers ever can point to the same object in +memory. There are many different algorithms for alias analysis and many +different ways of classifying them: flow-sensitive vs flow-insensitive, +context-sensitive vs context-insensitive, field-sensitive vs field-insensitive, +unification-based vs subset-based, etc. Traditionally, alias analyses respond +to a query with a Must, May, or No alias response, +indicating that two pointers always point to the same object, might point to the +same object, or are known to never point to the same object.

+ +

The LLVM AliasAnalysis +class is the primary interface used by clients and implementations of alias +analyses in the LLVM system. This class is the common interface between clients +of alias analysis information and the implementations providing it, and is +designed to support a wide range of implementations and clients (but currently +all clients are assumed to be flow-insensitive). In addition to simple alias +analysis information, this class exposes Mod/Ref information from those +implementations which can provide it, allowing for powerful analyses and +transformations to work well together.

+ +

This document contains information necessary to successfully implement this +interface, use it, and to test both sides. It also explains some of the finer +points about what exactly results mean. If you feel that something is unclear +or should be added, please let me +know.

+ +
+ + +
+ AliasAnalysis Class Overview +
+ + +
+ +

The AliasAnalysis +class defines the interface that the various alias analysis implementations +should support. This class exports two important enums: AliasResult +and ModRefResult which represent the result of an alias query or a +mod/ref query, respectively.

+ +

The AliasAnalysis interface exposes information about memory, +represented in several different ways. In particular, memory objects are +represented as a starting address and size, and function calls are represented +as the actual call or invoke instructions that performs the +call. The AliasAnalysis interface also exposes some helper methods +which allow you to get mod/ref information for arbitrary instructions.

+ +
+ + +
+ Representation of Pointers +
+ +
+ +

Most importantly, the AliasAnalysis class provides several methods +which are used to query whether or not two memory objects alias, whether +function calls can modify or read a memory object, etc. For all of these +queries, memory objects are represented as a pair of their starting address (a +symbolic LLVM Value*) and a static size.

+ +

Representing memory objects as a starting address and a size is critically +important for correct Alias Analyses. For example, consider this (silly, but +possible) C code:

+ +
+
+int i;
+char C[2];
+char A[10]; 
+/* ... */
+for (i = 0; i != 10; ++i) {
+  C[0] = A[i];          /* One byte store */
+  C[1] = A[9-i];        /* One byte store */
+}
+
+
+ +

In this case, the basicaa pass will disambiguate the stores to +C[0] and C[1] because they are accesses to two distinct +locations one byte apart, and the accesses are each one byte. In this case, the +LICM pass can use store motion to remove the stores from the loop. In +constrast, the following code:

+ +
+
+int i;
+char C[2];
+char A[10]; 
+/* ... */
+for (i = 0; i != 10; ++i) {
+  ((short*)C)[0] = A[i];  /* Two byte store! */
+  C[1] = A[9-i];          /* One byte store */
+}
+
+
+ +

In this case, the two stores to C do alias each other, because the access to +the &C[0] element is a two byte access. If size information wasn't +available in the query, even the first case would have to conservatively assume +that the accesses alias.

+ +
+ + +
+ The alias method +
+ +
+The alias method is the primary interface used to determine whether or +not two memory objects alias each other. It takes two memory objects as input +and returns MustAlias, MayAlias, or NoAlias as appropriate. +
+ + +
+ Must, May, and No Alias Responses +
+ +
+

The NoAlias response is used when the two pointers refer to distinct objects, +regardless of whether the pointers compare equal. For example, freed pointers +don't alias any pointers that were allocated afterwards. As a degenerate case, +pointers returned by malloc(0) have no bytes for an object, and are considered +NoAlias even when malloc returns the same pointer. The same rule applies to +NULL pointers.

+ +

The MayAlias response is used whenever the two pointers might refer to the +same object. If the two memory objects overlap, but do not start at the same +location, return MayAlias.

+ +

The MustAlias response may only be returned if the two memory objects are +guaranteed to always start at exactly the same location. A MustAlias response +implies that the pointers compare equal.

+ +
+ + +
+ The getModRefInfo methods +
+ +
+ +

The getModRefInfo methods return information about whether the +execution of an instruction can read or modify a memory location. Mod/Ref +information is always conservative: if an instruction might read or write +a location, ModRef is returned.

+ +

The AliasAnalysis class also provides a getModRefInfo +method for testing dependencies between function calls. This method takes two +call sites (CS1 & CS2), returns NoModRef if the two calls refer to disjoint +memory locations, Ref if CS1 reads memory written by CS2, Mod if CS1 writes to +memory read or written by CS2, or ModRef if CS1 might read or write memory +accessed by CS2. Note that this relation is not commutative.

+ +
+ + + +
+ Other useful AliasAnalysis methods +
+ +
+ +

+Several other tidbits of information are often collected by various alias +analysis implementations and can be put to good use by various clients. +

+ +
+ + +
+ The pointsToConstantMemory method +
+ +
+ +

The pointsToConstantMemory method returns true if and only if the +analysis can prove that the pointer only points to unchanging memory locations +(functions, constant global variables, and the null pointer). This information +can be used to refine mod/ref information: it is impossible for an unchanging +memory location to be modified.

+ +
+ + +
+ The doesNotAccessMemory and + onlyReadsMemory methods +
+ +
+ +

These methods are used to provide very simple mod/ref information for +function calls. The doesNotAccessMemory method returns true for a +function if the analysis can prove that the function never reads or writes to +memory, or if the function only reads from constant memory. Functions with this +property are side-effect free and only depend on their input arguments, allowing +them to be eliminated if they form common subexpressions or be hoisted out of +loops. Many common functions behave this way (e.g., sin and +cos) but many others do not (e.g., acos, which modifies the +errno variable).

+ +

The onlyReadsMemory method returns true for a function if analysis +can prove that (at most) the function only reads from non-volatile memory. +Functions with this property are side-effect free, only depending on their input +arguments and the state of memory when they are called. This property allows +calls to these functions to be eliminated and moved around, as long as there is +no store instruction that changes the contents of memory. Note that all +functions that satisfy the doesNotAccessMemory method also satisfies +onlyReadsMemory.

+ +
+ + +
+ Writing a new AliasAnalysis Implementation +
+ + +
+ +

Writing a new alias analysis implementation for LLVM is quite +straight-forward. There are already several implementations that you can use +for examples, and the following information should help fill in any details. +For a examples, take a look at the various alias analysis +implementations included with LLVM.

+ +
+ + +
+ Different Pass styles +
+ +
+ +

The first step to determining what type of LLVM pass you need to use for your Alias +Analysis. As is the case with most other analyses and transformations, the +answer should be fairly obvious from what type of problem you are trying to +solve:

+ +
    +
  1. If you require interprocedural analysis, it should be a + Pass.
    2. +
  2. If you are a function-local analysis, subclass FunctionPass.
    3. +
  3. If you don't need to look at the program at all, subclass + ImmutablePass.
    4. +
+ +

In addition to the pass that you subclass, you should also inherit from the +AliasAnalysis interface, of course, and use the +RegisterAnalysisGroup template to register as an implementation of +AliasAnalysis.

+ +
+ + +
+ Required initialization calls +
+ +
+ +

Your subclass of AliasAnalysis is required to invoke two methods on +the AliasAnalysis base class: getAnalysisUsage and +InitializeAliasAnalysis. In particular, your implementation of +getAnalysisUsage should explicitly call into the +AliasAnalysis::getAnalysisUsage method in addition to doing any +declaring any pass dependencies your pass has. Thus you should have something +like this:

+ +
+
+void getAnalysisUsage(AnalysisUsage &AU) const {
+  AliasAnalysis::getAnalysisUsage(AU);
+  // declare your dependencies here.
+}
+
+
+ +

Additionally, your must invoke the InitializeAliasAnalysis method +from your analysis run method (run for a Pass, +runOnFunction for a FunctionPass, or InitializePass +for an ImmutablePass). For example (as part of a Pass):

+ +
+
+bool run(Module &M) {
+  InitializeAliasAnalysis(this);
+  // Perform analysis here...
+  return false;
+}
+
+
+ +
+ + +
+ Interfaces which may be specified +
+ +
+ +

All of the AliasAnalysis +virtual methods default to providing chaining to another +alias analysis implementation, which ends up returning conservatively correct +information (returning "May" Alias and "Mod/Ref" for alias and mod/ref queries +respectively). Depending on the capabilities of the analysis you are +implementing, you just override the interfaces you can improve.

+ +
+ + + + +
+ AliasAnalysis chaining behavior +
+ +
+ +

With only two special exceptions (the basicaa and no-aa +passes) every alias analysis pass chains to another alias analysis +implementation (for example, the user can specify "-basicaa -ds-aa +-licm" to get the maximum benefit from both alias +analyses). The alias analysis class automatically takes care of most of this +for methods that you don't override. For methods that you do override, in code +paths that return a conservative MayAlias or Mod/Ref result, simply return +whatever the superclass computes. For example:

+ +
+
+AliasAnalysis::AliasResult alias(const Value *V1, unsigned V1Size,
+                                 const Value *V2, unsigned V2Size) {
+  if (...)
+    return NoAlias;
+  ...
+
+  // Couldn't determine a must or no-alias result.
+  return AliasAnalysis::alias(V1, V1Size, V2, V2Size);
+}
+
+
+ +

In addition to analysis queries, you must make sure to unconditionally pass +LLVM update notification methods to the superclass as +well if you override them, which allows all alias analyses in a change to be +updated.

+ +
+ + + +
+ Updating analysis results for transformations +
+ +
+

+Alias analysis information is initially computed for a static snapshot of the +program, but clients will use this information to make transformations to the +code. All but the most trivial forms of alias analysis will need to have their +analysis results updated to reflect the changes made by these transformations. +

+ +

+The AliasAnalysis interface exposes two methods which are used to +communicate program changes from the clients to the analysis implementations. +Various alias analysis implementations should use these methods to ensure that +their internal data structures are kept up-to-date as the program changes (for +example, when an instruction is deleted), and clients of alias analysis must be +sure to call these interfaces appropriately. +

+
+ + +
The deleteValue method
+ +
+The deleteValue method is called by transformations when they remove an +instruction or any other value from the program (including values that do not +use pointers). Typically alias analyses keep data structures that have entries +for each value in the program. When this method is called, they should remove +any entries for the specified value, if they exist. +
+ + +
The copyValue method
+ +
+The copyValue method is used when a new value is introduced into the +program. There is no way to introduce a value into the program that did not +exist before (this doesn't make sense for a safe compiler transformation), so +this is the only way to introduce a new value. This method indicates that the +new value has exactly the same properties as the value being copied. +
+ + +
The replaceWithNewValue method
+ +
+This method is a simple helper method that is provided to make clients easier to +use. It is implemented by copying the old analysis information to the new +value, then deleting the old value. This method cannot be overridden by alias +analysis implementations. +
+ + +
+ Efficiency Issues +
+ +
+ +

From the LLVM perspective, the only thing you need to do to provide an +efficient alias analysis is to make sure that alias analysis queries are +serviced quickly. The actual calculation of the alias analysis results (the +"run" method) is only performed once, but many (perhaps duplicate) queries may +be performed. Because of this, try to move as much computation to the run +method as possible (within reason).

+ +
+ + +
+ Using alias analysis results +
+ + +
+ +

There are several different ways to use alias analysis results. In order of +preference, these are...

+ +
+ + +
+ Using the MemoryDependenceAnalysis Pass +
+ +
+ +

The memdep pass uses alias analysis to provide high-level dependence +information about memory-using instructions. This will tell you which store +feeds into a load, for example. It uses caching and other techniques to be +efficient, and is used by Dead Store Elimination, GVN, and memcpy optimizations. +

+ +
+ + +
+ Using the AliasSetTracker class +
+ +
+ +

Many transformations need information about alias sets that are active +in some scope, rather than information about pairwise aliasing. The AliasSetTracker class +is used to efficiently build these Alias Sets from the pairwise alias analysis +information provided by the AliasAnalysis interface.

+ +

First you initialize the AliasSetTracker by using the "add" methods +to add information about various potentially aliasing instructions in the scope +you are interested in. Once all of the alias sets are completed, your pass +should simply iterate through the constructed alias sets, using the +AliasSetTracker begin()/end() methods.

+ +

The AliasSets formed by the AliasSetTracker are guaranteed +to be disjoint, calculate mod/ref information and volatility for the set, and +keep track of whether or not all of the pointers in the set are Must aliases. +The AliasSetTracker also makes sure that sets are properly folded due to call +instructions, and can provide a list of pointers in each set.

+ +

As an example user of this, the Loop +Invariant Code Motion pass uses AliasSetTrackers to calculate alias +sets for each loop nest. If an AliasSet in a loop is not modified, +then all load instructions from that set may be hoisted out of the loop. If any +alias sets are stored to and are must alias sets, then the stores may be +sunk to outside of the loop, promoting the memory location to a register for the +duration of the loop nest. Both of these transformations only apply if the +pointer argument is loop-invariant.

+ +
+ + +
+ The AliasSetTracker implementation +
+ +
+ +

The AliasSetTracker class is implemented to be as efficient as possible. It +uses the union-find algorithm to efficiently merge AliasSets when a pointer is +inserted into the AliasSetTracker that aliases multiple sets. The primary data +structure is a hash table mapping pointers to the AliasSet they are in.

+ +

The AliasSetTracker class must maintain a list of all of the LLVM Value*'s +that are in each AliasSet. Since the hash table already has entries for each +LLVM Value* of interest, the AliasesSets thread the linked list through these +hash-table nodes to avoid having to allocate memory unnecessarily, and to make +merging alias sets extremely efficient (the linked list merge is constant time). +

+ +

You shouldn't need to understand these details if you are just a client of +the AliasSetTracker, but if you look at the code, hopefully this brief +description will help make sense of why things are designed the way they +are.

+ +
+ + +
+ Using the AliasAnalysis interface directly +
+ +
+ +

If neither of these utility class are what your pass needs, you should use +the interfaces exposed by the AliasAnalysis class directly. Try to use +the higher-level methods when possible (e.g., use mod/ref information instead of +the alias method directly if possible) to get the +best precision and efficiency.

+ +
+ + +
+ Existing alias analysis implementations and clients +
+ + +
+ +

If you're going to be working with the LLVM alias analysis infrastructure, +you should know what clients and implementations of alias analysis are +available. In particular, if you are implementing an alias analysis, you should +be aware of the the clients that are useful +for monitoring and evaluating different implementations.

+ +
+ + +
+ Available AliasAnalysis implementations +
+ +
+ +

This section lists the various implementations of the AliasAnalysis +interface. With the exception of the -no-aa and +-basicaa implementations, all of these chain to other alias analysis implementations.

+ +
+ + +
+ The -no-aa pass +
+ +
+ +

The -no-aa pass is just like what it sounds: an alias analysis that +never returns any useful information. This pass can be useful if you think that +alias analysis is doing something wrong and are trying to narrow down a +problem.

+ +
+ + +
+ The -basicaa pass +
+ +
+ +

The -basicaa pass is the default LLVM alias analysis. It is an +aggressive local analysis that "knows" many important facts:

+ + + +
+ + +
+ The -globalsmodref-aa pass +
+ +
+ +

This pass implements a simple context-sensitive mod/ref and alias analysis +for internal global variables that don't "have their address taken". If a +global does not have its address taken, the pass knows that no pointers alias +the global. This pass also keeps track of functions that it knows never access +memory or never read memory. This allows certain optimizations (e.g. GVN) to +eliminate call instructions entirely. +

+ +

The real power of this pass is that it provides context-sensitive mod/ref +information for call instructions. This allows the optimizer to know that +calls to a function do not clobber or read the value of the global, allowing +loads and stores to be eliminated.

+ +

Note that this pass is somewhat limited in its scope (only support +non-address taken globals), but is very quick analysis.

+
+ + +
+ The -steens-aa pass +
+ +
+ +

The -steens-aa pass implements a variation on the well-known +"Steensgaard's algorithm" for interprocedural alias analysis. Steensgaard's +algorithm is a unification-based, flow-insensitive, context-insensitive, and +field-insensitive alias analysis that is also very scalable (effectively linear +time).

+ +

The LLVM -steens-aa pass implements a "speculatively +field-sensitive" version of Steensgaard's algorithm using the Data +Structure Analysis framework. This gives it substantially more precision than +the standard algorithm while maintaining excellent analysis scalability.

+ +

Note that -steens-aa is available in the optional "poolalloc" +module, it is not part of the LLVM core.

+ +
+ + +
+ The -ds-aa pass +
+ +
+ +

The -ds-aa pass implements the full Data Structure Analysis +algorithm. Data Structure Analysis is a modular unification-based, +flow-insensitive, context-sensitive, and speculatively +field-sensitive alias analysis that is also quite scalable, usually at +O(n*log(n)).

+ +

This algorithm is capable of responding to a full variety of alias analysis +queries, and can provide context-sensitive mod/ref information as well. The +only major facility not implemented so far is support for must-alias +information.

+ +

Note that -ds-aa is available in the optional "poolalloc" +module, it is not part of the LLVM core.

+ +
+ + + +
+ Alias analysis driven transformations +
+ +
+LLVM includes several alias-analysis driven transformations which can be used +with any of the implementations above. +
+ + +
+ The -adce pass +
+ +
+ +

The -adce pass, which implements Aggressive Dead Code Elimination +uses the AliasAnalysis interface to delete calls to functions that do +not have side-effects and are not used.

+ +
+ + + +
+ The -licm pass +
+ +
+ +

The -licm pass implements various Loop Invariant Code Motion related +transformations. It uses the AliasAnalysis interface for several +different transformations:

+ + + +
+ + +
+ The -argpromotion pass +
+ +
+

+The -argpromotion pass promotes by-reference arguments to be passed in +by-value instead. In particular, if pointer arguments are only loaded from it +passes in the value loaded instead of the address to the function. This pass +uses alias information to make sure that the value loaded from the argument +pointer is not modified between the entry of the function and any load of the +pointer.

+
+ + +
+ The -gvn, -memcpyopt, and -dse + passes +
+ +
+ +

These passes use AliasAnalysis information to reason about loads and stores. +

+ +
+ + +
+ Clients for debugging and evaluation of + implementations +
+ +
+ +

These passes are useful for evaluating the various alias analysis +implementations. You can use them with commands like 'opt -ds-aa +-aa-eval foo.bc -disable-output -stats'.

+ +
+ + +
+ The -print-alias-sets pass +
+ +
+ +

The -print-alias-sets pass is exposed as part of the +opt tool to print out the Alias Sets formed by the AliasSetTracker class. This is useful if you're using +the AliasSetTracker class. To use it, use something like:

+ +
+
+% opt -ds-aa -print-alias-sets -disable-output
+
+
+ +
+ + + +
+ The -count-aa pass +
+ +
+ +

The -count-aa pass is useful to see how many queries a particular +pass is making and what responses are returned by the alias analysis. As an +example,

+ +
+
+