tobast/phd-thesis
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity

Full check of analyse -> analyze

Browse source
This commit is contained in:
Théophile Bastian 2024-08-15 19:14:29 +02:00
parent 8d4887cc63
commit 4100d36c44
1 changed files with 2 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
manuscrit/20_foundations/20_code_analyzers.tex
View file

@ -89,9 +89,9 @@ point towards the resources that are limiting the kernel's performance, or
\paragraph{Static vs.\ dynamic analyzers.} Tools analyzing code, and code \paragraph{Static vs.\ dynamic analyzers.} Tools analyzing code, and code
analyzers among them, are generally either performing \emph{static} or analyzers among them, are generally either performing \emph{static} or
\emph{dynamic} analyses. Static analysers work on the program itself, be it \emph{dynamic} analyses. Static analyzers work on the program itself, be it
source code, assembly or any representation, without running it; while dynamic source code, assembly or any representation, without running it; while dynamic
analysers run the analyzed program, keeping it under scrutiny through either analyzers run the analyzed program, keeping it under scrutiny through either
instrumentation, monitoring or any relevant technique. Some analyzers mix both instrumentation, monitoring or any relevant technique. Some analyzers mix both
strategies to further refine their analyses. As a general rule of thumb, strategies to further refine their analyses. As a general rule of thumb,
dynamic analyzers are typically more accurate, being able to study the actual dynamic analyzers are typically more accurate, being able to study the actual