Updating manual and AUTHORS

This commit is contained in:
Andrey Voroshilov 2020-07-13 01:41:25 -07:00
parent 4c397ebe1e
commit bd5d965023
2 changed files with 5 additions and 0 deletions

View File

@ -10,3 +10,4 @@ Michał Cichoń <michcic@gmail.com> (OSX call stack decoding b
Thales Sabino <thales@codeplay.com> (OpenCL support) Thales Sabino <thales@codeplay.com> (OpenCL support)
Andrew Depke <andrewdepke@gmail.com> (Direct3D 12 support) Andrew Depke <andrewdepke@gmail.com> (Direct3D 12 support)
Simonas Kazlauskas <git@kazlauskas.me> (OSX CI, external bindings) Simonas Kazlauskas <git@kazlauskas.me> (OSX CI, external bindings)
Andrey Voroshilov <andrew.voroshilov@gmail.com> (multi-DLL fixes)

View File

@ -426,6 +426,10 @@ For that you need a \emph{profiler DLL} to which your executable and the other D
If you are targeting Windows with Microsoft Visual Studio or MinGW, add the \texttt{TRACY\_IMPORTS} define to your application. If you are targeting Windows with Microsoft Visual Studio or MinGW, add the \texttt{TRACY\_IMPORTS} define to your application.
If you are experiencing crashes or freezes when manually loading/unloading a separate DLL with Tracy integration, you might want to try defining both \texttt{TRACY\_DELAYED\_INIT} and \texttt{TRACY\_MANUAL\_LIFETIME} macros.
\texttt{TRACY\_DELAYED\_INIT} enables a path where profiler data is gathered into one structure and initialized on the first request rather than statically at the DLL load at the expense of atomic load on each request to the profiler data. \texttt{TRACY\_MANUAL\_LIFETIME} flag augments this behavior to provide manual \texttt{StartupProfiler} and \texttt{ShutdownProfiler} functions that allow you to manually create and destroy the profiler data, removing the need to do an atomic load on each call, as well as letting you define an appropriate place to free the resources.
\subsubsection{Problematic platforms} \subsubsection{Problematic platforms}
Some OS vendors think that \emph{they} own and control the devices \emph{you} have paid for. This results in restricting usage of APIs that might 'confuse' you, or denying you access to information about what your computer is doing. Some OS vendors think that \emph{they} own and control the devices \emph{you} have paid for. This results in restricting usage of APIs that might 'confuse' you, or denying you access to information about what your computer is doing.