New data structures with new features might also be developed. For RT applications, the language control structures might also be modified to provide a higher
level of control and timing conformance during program execution.
A programming language can be described by means of control structures,
presentation of data types, and the realization of sequential and conditional
expressions. For example, typical data structures are arrays, strings, files, and
records as above.
Implementation of the property limits or excludes some of currently “conventional” solutions or structures: files as data structure are no longer applicable and,
for example, should be replaced by new array structure. The best-fit idea so far was
suggested by Dr. Felix Friedrich ETH Zurich [4].
Implementation of this language data construct and support for it at the hardware
level enables us to activate (and power) only sections of memory that will be in
current use, thus providing when necessary energy-smart functioning.
At the same time, we are able to reconfigure data and duplicate data segments
when we feel it is required for reliability purposes.
Above all access, with fine-tuning of addresses—smaller domain on Fig. 6.3
makes performance of program with this data structure an order of magnitude faster
than even assembler code in conventional system.
Then development of data structures for evolving architectures would now seem
to lay in extension of array structures with different data types of elements, where
each element of data sequence is accompanied by type specifier providing enormous flexibility and even dynamic modification by the application or runtime
system and hardware conditions during program operation.
For fault-tolerant systems, where external events cause internal malfunctions
and/or necessitate reconfiguration for PRE requirements of applications, we have to
avoid hangs of the program and other uncertainties of the system. Thus, language
control operators and their interpretations through hardware instructions (as well as
operators themselves) should be organized with the following objectives:
Fig. 6.2 Modification of data structure limited by application domain
62
6 System Software Support for Hardware Deficiency…
level of control and timing conformance during program execution.
A programming language can be described by means of control structures,
presentation of data types, and the realization of sequential and conditional
expressions. For example, typical data structures are arrays, strings, files, and
records as above.
Implementation of the property limits or excludes some of currently “conventional” solutions or structures: files as data structure are no longer applicable and,
for example, should be replaced by new array structure. The best-fit idea so far was
suggested by Dr. Felix Friedrich ETH Zurich [4].
Implementation of this language data construct and support for it at the hardware
level enables us to activate (and power) only sections of memory that will be in
current use, thus providing when necessary energy-smart functioning.
At the same time, we are able to reconfigure data and duplicate data segments
when we feel it is required for reliability purposes.
Above all access, with fine-tuning of addresses—smaller domain on Fig. 6.3
makes performance of program with this data structure an order of magnitude faster
than even assembler code in conventional system.
Then development of data structures for evolving architectures would now seem
to lay in extension of array structures with different data types of elements, where
each element of data sequence is accompanied by type specifier providing enormous flexibility and even dynamic modification by the application or runtime
system and hardware conditions during program operation.
For fault-tolerant systems, where external events cause internal malfunctions
and/or necessitate reconfiguration for PRE requirements of applications, we have to
avoid hangs of the program and other uncertainties of the system. Thus, language
control operators and their interpretations through hardware instructions (as well as
operators themselves) should be organized with the following objectives:
Fig. 6.2 Modification of data structure limited by application domain
62
6 System Software Support for Hardware Deficiency…