DirectXShaderCompiler/docs
Kirill Kozlov 38fcd6f741
[SPIRV] Add option to preserve interface variables (#5400)
Add `-fspv-preserve-interface` CLI option to prevent DCE optimization
pass from compiling out interface variables. It happens if these
variables are unused.

The option may be useful when decompiling SPIR-V back to HLSL.
Personally, I need it to convert DX12 shaders to DX11 ones using
SPIRV-Cross as a tool for converting SPIR-V, produced by DXC, to the old
shader model HLSL.

SPIR-V Tools now have a parameter in `RegisterPerformancePasses()` and
`RegisterLegalizationPasses()` for this. This PR creates a new command
line option in DXC and passes it to the `spvtools::Optimizer`.

Closes #4567
2023-07-11 12:20:58 +02:00
..
CommandGuide [lit] Port Support %if ... %else syntax for RUN lines from upstream (#5227) 2023-05-26 14:10:34 -07:00
Frontend
TableGen
_static
_templates
_themes/dxc-theme
AliasAnalysis.rst
Atomics.rst
BitCodeFormat.rst
BitSets.rst
BlockFrequencyTerminology.rst
BranchWeightMetadata.rst
BuildingAndTestingDXC.rst Enable lit by default. (#5133) 2023-06-05 10:35:24 -07:00
CMake.rst
CMakeLists.txt
CodeGenerator.rst
CodingStandards.rst
CommandLine.rst
CoverageMappingFormat.rst
DXIL.rst Validate no gaps in UAV store writemask (#4495) 2022-06-03 10:39:00 -07:00
Dummy.html
ExceptionHandling.rst
ExtendingLLVM.rst
FaultMaps.rst
GetElementPtr.rst
HLSLChanges.rst
HowToSetUpLLVMStyleRTTI.rst
HowToUseAttributes.rst
HowToUseInstrMappings.rst
InAlloca.rst
LLVMBuild.rst
LLVMBuild.txt
LangRef.rst
Lexicon.rst
LibFuzzer.rst
LinkTimeOptimization.rst
Makefile.sphinx
MarkedUpDisassembly.rst
MergeFunctions.rst
Passes.rst
ProgrammersManual.rst
README.txt
SPIR-V.rst [SPIRV] Add option to preserve interface variables (#5400) 2023-07-11 12:20:58 +02:00
SPIRV-Cookbook.rst Rename master branch to main (#4461) 2022-05-16 15:00:19 -07:00
SourceLevelDebugging.rst
SourceLevelDebuggingHLSL.rst
SystemLibrary.rst
Vectorizers.rst
WritingAnLLVMBackend.rst
WritingAnLLVMPass.rst
YamlIO.rst
conf.py
index.rst
make.bat

README.txt

LLVM Documentation
==================

LLVM's documentation is written in reStructuredText, a lightweight
plaintext markup language (file extension `.rst`). While the
reStructuredText documentation should be quite readable in source form, it
is mostly meant to be processed by the Sphinx documentation generation
system to create HTML pages which are hosted on <http://llvm.org/docs/> and
updated after every commit. Manpage output is also supported, see below.

If you instead would like to generate and view the HTML locally, install
Sphinx <http://sphinx-doc.org/> and then do:

    cd docs/
    make -f Makefile.sphinx
    $BROWSER _build/html/index.html

The mapping between reStructuredText files and generated documentation is
`docs/Foo.rst` <-> `_build/html/Foo.html` <-> `http://llvm.org/docs/Foo.html`.

If you are interested in writing new documentation, you will want to read
`SphinxQuickstartTemplate.rst` which will get you writing documentation
very fast and includes examples of the most important reStructuredText
markup syntax.

Manpage Output
===============

Building the manpages is similar to building the HTML documentation. The
primary difference is to use the `man` makefile target, instead of the
default (which is `html`). Sphinx then produces the man pages in the
directory `_build/man/`.

    cd docs/
    make -f Makefile.sphinx man
    man -l _build/man/FileCheck.1

The correspondence between .rst files and man pages is
`docs/CommandGuide/Foo.rst` <-> `_build/man/Foo.1`.
These .rst files are also included during HTML generation so they are also
viewable online (as noted above) at e.g.
`http://llvm.org/docs/CommandGuide/Foo.html`.

Checking links
==============

The reachibility of external links in the documentation can be checked by
running:

    cd docs/
    make -f Makefile.sphinx linkcheck