Hello, Arsen. Shnurkov, you wrote:>> 2) AS> and correctly do not understand. Because there are no the estimates painting how much becomes worse and for the account of that. Deceleration can is comprehensible? Can , can not . A problem that about the deceleration which has happened because of the bad alignment, nobody notifies. Neither the compiler, nor an operating system, the processor. By the way, in mobile devices "deceleration" == "the raised expenditure of a battery".>> 3) has interesting consequences of that type that atomic operations with incorrectly aligned word it is unexpected and without the warning cease to be atomic AS> not that case. With lines all the same you will not work, it is for this purpose necessary separate lock, which and so on boundary something there. Here a problem that absolutely correct by sight InterlockedIncrement () can appear actually not Interlocked, that the data is incorrectly aligned. And this problem no means always will be shown. Who from programmers generally in course what between elementary quality and alignment there is a communication?>> 4) AS> personally to me brings pleasure, happiness and storage saving (for the account of insignificant lowering of high-speed performance) Well actually, no. Because at first Hindus the brake code. And then, when brakes become intolerable, employ other Hindus whom all accelerate, at the expense of aggressive the intermediate results (because the code generating these results passes by then in a state "do not touch, will not stink", and it nobody dares to optimize). Therefore as a result will be both slowly, and it is gluttonous on storage.