see compiler generated code

[mkorobko]

I was wondering if there is a way to see the source code generated by
compiler - anything that compiler inserts such as constructors,
destructors, vptr, etc . Looking at this can help to learn.

 

[Phlip]

I was wondering if there is a way to see the source code generated by

compiler - anything that compiler inserts such as constructors,
destructors, vptr, etc . Looking at this can help to learn.

This is one of those questions where you will also get good answers from the
forum covering your own compiler.

I would...

- debug the code and step into each method
- debug with the disassembly turned on, so you can see the opcodes
- use cfront, IIRC, to turn the C++ into C, with all the C++ features
hanging out
- debug that!

 

[mkorobko]

This is one of those questions where you will also get good answers from the
forum covering your own compiler.

I would...

 - debug the code and step into each method
 - debug with the disassembly turned on, so you can see the opcodes
 - use cfront, IIRC, to turn the C++ into C, with all the C++ features
hanging out
 - debug that!

Thank you.

 

[Phlip]

- use cfront, IIRC

It was a rhetorical question.

http://www.google.com/search?q=IIRC

 

[Bart van Ingen Schenau]

I was wondering if there is a way to see the source code generated by
compiler - anything that compiler inserts such as constructors,
destructors, vptr, etc . Looking at this can help to learn.

No, you can't obtain any source code for the compiler-generated parts
of the program, because the compiler does not create source code for
that.
The best you can get is to ask the compiler to output (annotated)
assembly code, but be aware that optimisations can make it very hard
to recognise your own code in the produced assembly.

Bart v Ingen Schenau

 

[mkorobko]

No, you can't obtain any source code for the compiler-generated parts
of the program, because the compiler does not create source code for
that.
The best you can get is to ask the compiler to output (annotated)
assembly code, but be aware that optimisations can make it very hard
to recognise your own code in the produced assembly.

Bart v Ingen Schenau

Thanks everyone for your replies. It was helpful.