-Neglect dynamic methods of optimization (a prediction of passages, hardware etc.);
So time talk came about errors into architecture implementations any hardware optimization complicates a construction and increases probability of an error, which leads to that it is necessary to reduce frequency and productivity to provide reliable functioning of the processor.
I do not understand that means, when here speak about errors by development. I assume that for the Russian organization it is difficult to provide, that the processor generally earned, it is difficult to provide control of correctness of passage of all development cycles of the designer documentation, not to pass any important trifle because of which it is necessary to alter all, and time and means for it any more will not be. The problem in that though something to make operating is in itself very difficultly. It is visible that at us very few people undertakes to develop rather productive processors completely.
It is how much easy to connect dynamic methods of optimization to optimization at a compilation stage is other question. The trivial thought which here comes to mind - that at performance of the same function by two mechanisms simultaneously can arise their interference, palpation, and they will sometimes strengthen the effect, and sometimes and to bring to naught. The in itself combination of two mechanisms demands presence of some of the third, something like the damper. It is more than miscellaneous in system - does not mean better.
It at level of the most general reasonings. It is necessary was specific to look in architecture to understand, whether dynamic optimization and if helps, where helps it.
As though it was no question to the main lines of architecture, instead of how the organization with potentially developers implements it.
Adding from 12/11/2016 01:22:
-Choice [del] Vanderbildihi [/del] Intel as the sample for imitation,
In this branch of Intel too the sample.
Adding from 12/11/2016 01:38:
-Closeness of systems of development and inaccessibility of Elbrus for independent and access of enthusiasts;
it is possible, development in such state that enthusiasts-singles do not help it. And for the organizations of closeness is not present - customers receive and test. Another matter that is such users who do system for itself, instead of for sale by all interested person. But, on the other hand, who can wish to buy Elbrus when in shops machines on processors with OS are generally available? What for to try for the sake of few enthusiasts who do not represent solvent demand on on microprocessors.
Probably, it is important to fulfill the orders defining well-being of the organization.
It is possible to assume that the organization already has long enough list of hardware both program bugs, and additional independent are not necessary yet.