Big Chemical Encyclopedia

Chemical substances, components, reactions, process design ...

Articles Figures Tables About

Binary executable program

Control flow checking, which can be implemented in hardware [15,9,6] or software [2,30,7,29], provides means to recognize invalid control flow for the executed program, that is, execution of sequences of instructions which are not permitted for the executed binary. In contrast to AN-encoding control flow checking cannot detect errors which do only influence processed data. [Pg.285]

The JOBNAME.47 archive file becomes the input file for yom GENNB05 job, which performs the actual NBO analysis. With the PC-Windows GENNB05.0W version, you merely launch the program by mouseclick and select the JOBNAME.47 job from the displayed menu selections. Alternatively, if the GENNB05 program has been set up as a binary executable (gennbo5.exe) on your system, you can launch the job by a command of the form... [Pg.2]

The sequence of instructions to be executed by the computer is called a program. In actuality, the program is a set of binary-coded instructions stored in memory. The CPU fetches each instruction from memory, interprets and executes it, and then moves on to the next instruction. The CPU fetches instructions sequentially from memory, unless told to do otherwise by one of the instructions. [Pg.713]

Other software approaches work with replicated execution and comparison of the obtained results. The protected software is modified during or before compilation—rarely, dynamic binary instrumentation is used [24]. Replication can be implemented at different levels of abstraction. Some approaches duplicate single instructions and execute them in one thread [22,19,10,25,24,6]. Other approaches execute duplicates of the whole program within several threads and provide synchronization means for them [31,12,32]. For all those approaches which are based on redimdant execution of the same program instructions, it is not possible to provide guarantees with respect to permanent hardware errors or soft errors which disturb the voting mechanism. [Pg.285]

For each register r, w(r) is denoted as its binary width (e.g. oj(r) = 32 in PISA), and the data-with of actual value stored in r is defined as zu(r), which depends on the concrete execution process of program. These execution profile and the data-width information of register value can be extracted from profiled execution, or generated from static approximations [14]. Previous work indicates that the data-width of registers value are highly predictable [15]. [Pg.127]

A safe upper bound of the maximal stack usage can be computed by whole-program sialic analysis al Ihe executable code level. When an abstract interpretation based static analyzer is used, it can be formally proven that the maximal stack usage of each task will never be underestimated. From the per-task stack maxima the system-level stack maximum can be determined from the priorities of the tasks and the interrupt hierarchy. The challenge for binary-code level analyzers is to minimize the necessary amount of user interactions, e.g., for function pointer calls. To minimize user interaction, the analysis has to be precise, and the annotation mechanism has to be flexible and easy-to-use. The analyzer configuration has to be done once for each software project afterwards the analysis can be run automatically, supporting continuous verification. [Pg.203]

A compiler is a computer program that translates high-level language statements into directly executable machine code. A single high-level statement generally results in many machine instructions. The compiler translates the machine code into binary code (O s and I s) for the computer to understand. [Pg.69]

An interpreter reads the program instructions written in a computer language and executes the computer language statements directly. This is as opposed to a compiler, which translates the statements into a binary format that is then independently available for execution. Interpreted code tends to run slower than compiled code. The interpreter must always be present in order to run the code, whereas the compiler does not have to be present after the code is compiled. The Basic language is an example of an interpreter and interpreted language. [Pg.227]


See other pages where Binary executable program is mentioned: [Pg.851]    [Pg.136]    [Pg.2]    [Pg.435]    [Pg.206]    [Pg.1411]    [Pg.3]    [Pg.529]    [Pg.3]    [Pg.529]    [Pg.315]    [Pg.264]    [Pg.78]    [Pg.128]    [Pg.187]    [Pg.389]    [Pg.366]    [Pg.713]    [Pg.12]    [Pg.276]    [Pg.71]    [Pg.2076]    [Pg.296]    [Pg.97]    [Pg.49]    [Pg.10]    [Pg.287]    [Pg.126]    [Pg.205]    [Pg.9]    [Pg.362]    [Pg.130]    [Pg.1406]   
See also in sourсe #XX -- [ Pg.2 ]




SEARCH



Executable program

Execution

Executive program

Program execution

© 2024 chempedia.info