Thus in reality i think it is rare and of no use. The writers of the compiler have done all that work already for you. You need to do this because you have to have full knowledge of the limitations of the cpu and of the advantages. If you want to write better assembly, you have to study the specific processor architecture you are coding for in assembly in detail. This means that the compiler knows exactly which combination of instructions when executed after each other extract maximum performance. This means that in advance, the compiler if optimized for a certain generation of cpu, that the compiler will know in advance all limitations of that cpu and advantages of that particular cpu. All taken from Wikipedia because it is something long forgotten.Īssume the code generated by the compiler to be very good.įor example the Intel compiler is written by Intel (duh). RISC is Reduced Instruction Set Computing, which deals with simplified instructions.
It seems that VLIW is type of architecture that uses instruction parallelism. RISC and VLIW are dealing with CPU architecture. Cannot really comment on how good the efficiency is, but normal user probably cannot tell much difference. Most compiler these days are optimized to work at fairly good efficiency. Another thing, for C++, it is called compiler, but Java is called interpreter as it runs the program directly, it does not compile, forgot the major difference between the two.
Also compiled codes are more suspectable to compiler fault, gcc compiler had that problem before.
Compiled code might be platform/compiler dependent, like Linux C codes might not work with Visual C++/C# and Visual C++ codes might not work with Borland C(are they still in business?), so adjustments might needed to be made. Compiled code will not be as hardware dependent because compiler took care of all those things in the background, and all the programmer has to worry is about writing workable codes. However, sometimes assembly code can only work with specific type of CPU, like code that specifically coded for Intel CPU would not necessarily work with AMD CPU and vice versa, unless they have compatible instructions that allows the code to work.Ĭompiled code needs to be compiled and interpreted into machine language then run. It is been a while so answers might be wrong.Īs Ancalagon44 said, assembly code is generally faster and most of time smaller because they deal more directly with instructions, system calls, and work with registers for storing values and strings and such, it is the closest thing to machine language.
0 kommentar(er)
