Object Code Accelerator Manual

Preparing Programs for Acceleration
Object Code Accelerator Manual—528144-003
3-11
Procedure Name Conflicts
BEGIN
INT a,b,c,d; ! Local variables
c := 1;
f[4] := c+100; ! Undefined on TNS/E systems
b := c+3;
END;
If you execute this program on a TNS system or as TNS code on a TNS/E system,
b = 104 at the end of the procedure. If you accelerate this program and then
execute it on a TNS/E system, b = 4.
Procedure Name Conflicts
A program can call several procedures of the same name, as long as each of the
procedures resides in a different code space. For example, a program can call a
system library procedure named File_Close_ and a user library procedure named
File_Close_. Each of these procedures can have a different return value size. OCA
must determine the return value size for all procedures called by a program. When
OCA processes such a program, it resolves the name conflict in favor of the system
library procedure. This can result in an incorrectly accelerated program. HP strongly
recommends that you do not give your procedures names that conflict with system
procedure names.