eldo_user

Eldo Control Language
Parallel Operation
Difference Between Sequential and Parallel Execution
The same task run with parallelism activated or deactivated should have exactly the same effect
except for the following two points:
• If outputs are printed by tasks run in parallel, then the order of the outputs is undefined.
If the order is important then you must not use fprint inside tasks run in parallel but
outside, for example in a loop run sequentially.
• A break used inside a loop run in parallel may cause differences between sequential and
parallel execution; see the section “Continue, Break and Return Parallel Behavior” on
page 1050.
Generated Netlists
For simulations run in parallel, if you specify the same netlist name for each simulation, ECL
changes it automatically to suffix it with the index of the job.
Waveforms
Inside the main wdb file, the names of waveforms generated by simulations run will be suffixed
by a unique index to avoid concurrency issues.
Debug Mode
When in debug mode (setenv ELDO_CL_DEBUG) when jobs are executed in parallel, their
debug outputs are mixed but they are prefixed with the index of the corresponding job to enable
better understanding.
Related Topics
Parallel Construct
Parallel Construct
The first parallel construct enables you to define tasks or functions (jobs) to be run in parallel.
The results of the tasks or functions are stored inside an array.
Para Function to Parallelize Tasks
See function “Identifying the Index of the Current Job” on page 1040.
Identifying the Index of the Current Job
For ease of use, it is possible to call the function ijob() to obtain the index of the current job.
Example: basic use of ijob():
1040
Eldo® User's Manual, 15.3