Editing LabVIEW (section)

=== Code compiling and execution ===
LabVIEW includes a [[compiler]] that translates "G" code into native code for supported CPU platforms. The graphical code is converted into Dataflow Intermediate Representation, and then translated into chunks of executable [[machine code]] by a compiler based on [[LLVM]]. These code chunks are called by the "G" [[Run-time system|run-time]] engine, providing for fast, high-performance native  execution of the graphical code. The LabVIEW syntax is strictly enforced during the editing process, and when "G" code is run or saved, the compiler is automatically invoked. "G" code is saved to a single binary file that contains both the source and executable code. Execution is controlled by the run-time engine, which contains some pre-compiled code to perform common tasks defined in the "G" language. The run-time engine manages execution flow, and provides a consistent interface to supported operating systems, graphic systems and hardware components. The use of a portable run-time environment makes the source code files portable across supported platforms. LabVIEW programs are slower than equivalent compiled C code, although it is often possible to mitigate speed issues with program optimizations.<ref>{{cite web|url=https://www.ni.com/pl-pl/support/documentation/supplemental/10/ni-labview-compiler--under-the-hood.html#section-1599648034|title=NI LabVIEW Compiler: Under the Hood|date=4 February 2020|website=ni.com}}</ref>