My understanding is that a compiler converts the high level language into machine code. I have a question as to whether a compiler(say VC++) in-turn uses an assembler too? I remember seeing assembly code, whenever there is a crash or something like that.
+1
A:
A compiler goes directly to machine code.
The debugger will show the machine code instructions as assembler, but the debugger can also show other code which wasn't compiled by the compiler.
The compiler may also include an assembler so you can include inline assembler code in with the higher level language or generate assembler output.
Martin Beckett
2010-06-20 17:32:00
not correct.... I could program a compiler that outputs only assembly source, to be assembled apart with an assembler... moreover, compiler hardly goes so _directly_ to machine code... internal representation (different from target machine cod) of the code (!) could be very useful to do optimization and so on... ok, everything likely is hidden, but "_directly_" is too much anyway! :D
ShinTakezou
2010-06-25 16:15:45
You could but to answer the OP's question Visual Studio doesn't output assembler and then call MASM to generate the exe
Martin Beckett
2010-06-25 16:50:07
+4
A:
It depends on the compiler; many compilers can compile to assembly. For instance, if you pass the '-S' flag to gcc, like:
gcc -S -o test.S test.c
That will output assembly for your test.c file into the file test.S which you can look at. (I recommend using -O0 if you're gonna be trying to read the assembly, because compiler optimizations in there will likely confuse the heck out of you).
Since you mentioned Visual C++ in your question, Paul Dixon points out below that Visual C++ uses the /FA flag to accomplish the same thing.
Adrian Petrescu
2010-06-20 17:35:09
Well, actually, mainly GCC does that :-) Most commercial ones have it buildin to avoid the slow generating/reparsing text step, with only an option to generate assembler if needed.
Marco van de Voort
2010-07-02 04:21:33
+1
A:
Most compilers will have an option to view an assembly listing
- VC can be told to output an assembler listing with /FA
- with gcc, use the -S switch
Paul Dixon
2010-06-20 17:36:26
A:
A compiler translates some high level programming language to some lower level language (as machine code, assembly or even another high level language, for example from Vala to C, or from uC++ to C++).
I don't know about VC++, but most compilers, as GNU GCC doensn't include an Assembler, but invoke an external Assembler program (as NASM, or GNU AS).
Cheers
Fernando
2010-06-20 18:07:50
+1
A:
In general, a compiler translates one language into another. Most compilers target machine code; here are the most common ways of doing this, in order from lowest-level to highest-level:
- Produce machine code directly, by including back-ends for each instruction set.
- Produce assembly language, which is passed to an external assembler. This is what gcc does. After all, why not use existing assemblers? Generating opcodes directly is a pain.
- Generate a low-level intermediate form of the code, such as LLVM bytecode, which gets transformed into machine code. LLVM is a godsend for compiler-writers, because it handles a vast number of optimizations and supports a lot of back-ends, while letting you write at a higher level than assembly.
- Transform the code into a language like C, and then pass it to another compiler. Facebook does this to PHP: they compile it to C++, and then use gcc to compile that to assembly, which is assembled to native code by GNU as.
If you'd like to try writing a compiler, I'd recommend starting off with something like C as the back-end. If you'd like to get more elaborate later, try LLVM. If you try to produce assembly language or machine code directly, it'll probably be less efficient than what a C compiler or LLVM would produce. I speak from embarrassing personal experience on this one.
Peter Scott
2010-06-20 18:26:26