1

Topic: x64 Commands in x32 to Windows environment

Whether it is possible for the compiler (VC or gcc) to prompt, what it used x64 commands if needed (with a prefix certainly) in x32 to Windows environment (and x32  it is finite)? It is necessary for acceleration of calculations over 64 bit numbers. If is not present, what candidate solutions of the given task are? In manual on  it is necessary to write much.

2

Re: x64 Commands in x32 to Windows environment

Hello, , you wrote: > Use commands FPU, integer numbers to 2 ** 64 there the exact. It likely brakes will be where as big, than in 32 bit numbers in normal registers to operate taking into account transfer and all affairs. Anyway while talk about addition and subtraction, with multiplication and division a question certainly interesting.

3

Re: x64 Commands in x32 to Windows environment

Whether M>> It is possible for the compiler (VC or gcc) to prompt, what it used x64 commands if needed (with a prefix certainly) in x32 to Windows environment (and x32  it is finite)? > Alas, but such prefixes which were at passage with 16 on 32, are not present now. 64-digit commands are recognized only in the 64-digit environment. , it is possible to pass in 64 the bit environment, to make that it is necessary, and to return back. But the compiler to such tricks certainly not to teach. Only , only a hardcore.

4

Re: x64 Commands in x32 to Windows environment

O>> Noooo, it is possible to pass in 64 the bit environment, to make that it is necessary, and to return back. O>> But the compiler to such tricks certainly not to teach. Only , only a hardcore. > at the time of MS-DOS something similar was possible, but there the environment scanty, as a matter of fact missed. In any Windows 10 expenses for switchings kill all scoring from 64-categories in the middle of 32 bit environments. Do not kill, such switchings happen at everyone  so if to do switching before what that long calculations that all will be  since switching in other mode it is simple far jump with some , and an overhead charge at it corresponding. With the compiler to potter too   it is not necessary, enough  fair 64 , but depending only from ntdll.dll, then by means of this trick (for modern  some correction is required)  it in  wow64 process, to receive the address of the necessary export and to pull them.

5

Re: x64 Commands in x32 to Windows environment

Hello, ononim, you wrote: O>>> Noooo, it is possible to pass in 64 the bit environment, to make that it is necessary, and to return back. O>>> But the compiler to such tricks certainly not to teach. Only , only a hardcore. >> at the time of MS-DOS something similar was possible, but there the environment scanty, as a matter of fact missed. In any Windows 10 expenses for switchings kill all scoring from 64-categories in the middle of 32 bit environments. O> do not kill, such switchings happen at everyone  so if to do switching before what that long calculations that all will be  since switching in other mode it is simple far jump with some , and an overhead charge at it corresponding. With the compiler to potter too   it is not necessary, enough  fair 64 , but depending only from ntdll.dll, then by means of this trick (for modern  some correction is required)  it in  wow64 process, to receive the address of the necessary export and to pull them. At us multinuclear processors. They can be generalized with each other and is in different modes simultaneously (one in long mode, another in compatibility and the third in real) or not?

6

Re: x64 Commands in x32 to Windows environment

_> At us multinuclear processors. They can be generalized with each other and is in different modes simultaneously (one in long mode, another in compatibility and the third in real) or not? Certainly, moreover - at execution wow64 process everyone  passes there-back 100500 times a second. For almost each system call in wow64 versions ntdll is implemented as switching in long mode, conversion of parameters, a call in a kernel through  ntdll and after reset - too most upside-down. Some  cause a kernel directly, but all the same there there is a switching in long mode. long mode is not goodness knows what, and only  the selector which is selected at present in cs. That is is a part of a context of a flow, as well as all remaining registers of the processor.

7

Re: x64 Commands in x32 to Windows environment

Hello, , you wrote: > Is also signals of interruptions to which it is necessary to react correctly. As a whole yes, it is possible to organize a compound 32+64, but for today, in my opinion, already there is no sense. It is necessary to write in the 64-digit environment and all. Here I do not agree. If application does not assume a survival of all juice from iron. That the program should be started up on any iron and not be fastidious. Especially if it something  and utilitarian. Otherwise the simple calculator  worked on 32 on 8  with 128 the RAM, will demand now 64 OS latest.net core and 20 the RAM what simply to add and subtract, ah and to swing last  at the moment of the code should fulfill the main functional. Though all to spit all stupidly behold. After all  the flies assured of without an inaccuracy, it  approves. > Fortunately, in the nearest billion years passage from 64 bit storages on 128-digit does not threaten Us here frighten that just about both  show the superiority and  networks change architecture. Look at digit capacity of buses of given videos of accelerators

8

Re: x64 Commands in x32 to Windows environment

Hello, , you wrote: > It is digit capacity of the data (for example, AVX-commands and registers), and I about digit capacity of addressing. Yes digit capacity of the bus of the data. > at first was 8086 with addressing 64, and storages - 1 Mb (yes, those 640 To which suffices all). > Then storage quickly exceeded 1 Mb. Then passed on 32, but also storage quickly exceeded 4. > Then passed on 64. And here  with 4 billion chips on 4 everyone is not foreseen yet So now 48 address bus, instead of 64. Thus everyones 8 microcontrollers with 128 storages  pores easy work.

9

Re: x64 Commands in x32 to Windows environment

Hello, kov_serg, you wrote: _> Us here frighten that just about both  show the superiority and  networks change architecture. Look at digit capacity of buses of given videos of accelerators TSPU now have the 64-bit bus on the channel (72-bit in case of ECC) that is what-thread i7 with fourline the storage controler de facto has the bus in width in 64*4=256 bit that any more so and it is not enough. And considering that DDR3/4 give the data only till eight portions for time (architecture 8n prefetch) each transaction of reading from storage produces at once 256*8=2048 bit of the data, and it is less than gram.

10

Re: x64 Commands in x32 to Windows environment

Hello, , you wrote: > For us passage of addressing with 32 on 64 was last. Therefore it is desirable to pass more likely in the 64-digit environment and to get used to it. Special cases of microcontrollers and small digit capacity concern only not so to the most part of programmers. The most part of programmers (write on , pythons, etc.) solve utilitarian tasks it digit capacity of the processor is not important. Especially to a customer it is deeply violet that there for a hogwash inside to be created, it should work and solve tasks in view. For remaining that would be got used a C ++ int in 64 a mode is equal 32 better