Lines Matching refs:backend

20 for C++, but may be any type of file that the backend developer needs.
22 This document is a guide to writing a backend for TableGen. It is not a
49 instance is passed to the backend when it is invoked by TableGen. This class
444 The following steps are required to create a new backend for TableGen.
446 #. Invent a name for your backend C++ file, say ``GenAddressModes``.
448 #. Write the new backend, using the file ``TableGenBackendSkeleton.cpp``
451 #. Determine which instance of TableGen requires the new backend. There is
455 #. Modify the selected ``tablegen.cpp`` to include your new backend.
463      function. It should invoke the "main function" of your backend, which
469 #. Add your backend C++ file to the appropriate ``CMakeLists.txt`` file so
478 unit for writing a new TableGen backend. Here are a few notes on the file.
493 * One function is named ``run``. It is invoked by the backend's "main
501 * The only function in the ``llvm`` namespace is the backend "main function."
673 included in the skeleton backend file ``TableGenBackendSkeleton.cpp``.
724 The TableGen command option ``--print-records`` invokes a simple backend
726 the default backend option. The format of the output is guaranteed to be
764 The TableGen command option ``--print-detailed-records`` invokes a backend
818 selected backend. This feature is enabled with the ``--time-phases`` option
821 If the backend is *not* instrumented for timing, then a report such as the
823 ``--print-detailed-records`` backend run on the AMDGPU target.
838 Note that all the time for the backend is lumped under "Backend overall".
840 If the backend is instrumented for timing, then its processing is
842 the ``--emit-dag-isel`` backend run on the AMDGPU target.
860 The backend has been divided into four phases and timed separately.
862 If you want to instrument a backend, refer to the backend ``DAGISelEmitter.cpp``