compiler-options

I am trying to learn assembly language. I have searched and found how to disassemble a .c file but I think it produces some optimized version of the program. Is there any way so that I can see the exact assembly code which corresponds to my C file. The gcc option -O enables different levels of optimization. Use -O0 to disable them and use -S to output assembly. -O3 is the highest level of optimization. Starting with gcc 4.8 the optimization level -Og is available. It enables optimizations that do not interfere with debugging and is the recommended default for the standard edit-compile-debug

This question is related to Instruct Cmake to use CXX and CXXFLAGS when driving link? In the former question, we are trying to instruct CMake to use CXXFLAGS when it invokes the linker. add_compile_options We found that the following code if (CMAKE_VERSION VERSION_LESS 2.8.12) add_definitions(-foo) else() add_compile_options(-foo) endif() message(STATUS, "CXXFLAGS: ${CMAKE_CXX_FLAGS}") produces the output CXXFLAGS: SET CMAKE_CXX_FLAGS We found that the following code SET(CMAKE_CXX_FLAGS "${CMAKE_CXX_FLAGS} -foo" ) message(STATUS, "CXXFLAGS: ${CMAKE_CXX_FLAGS}") produces the output CXXFLAGS:

What is the real difference between these two options? What I know is: Register for COM Interop This options executes regasm on the assembly and registers the assembly as an COM component(or maybe not) in the registry with all COM like registry entries. Does this step generates a TLB file? What else is done? Sometimes I see a tlb is generated when I compile the project but sometimes not, why is this? Make assembly COM visible What effect does this one has on an assembly? If I have the following type inside this assembly, do I still need to specify the "Make assembly COM Visible" even though my

Basically, I'm trying to understand the difference between the "Break in Class Module" and "Break on Unhandled Errors" that appear in the Visual Basic 6.0 IDE under the following path: Tools --> Options --> General --> Error Trapping The three options appear to be: Break on All Errors Break in Class Module Break on Unhandled Errors Now, apparently, according to MSDN, the second option (Break in Class Module) really just means "Break on Unhandled Errors in Class Modules". Also, this option appears to be set by default (ie: I think its set to this out of the box). What I am trying to figure out

Microsoft's C++ compiler ( cl.exe , as included with Visual Studio) offers several optimization switches . The difference between most of them seems self-explanatory, but it's not clear to me what the difference is between /O2 (which optimizes code for maximum speed) and /Ox (which selects "full optimization"). I've tried reading the documentation for the /Ox option, and it seems to confirm that this switch also enables optimizations for maximum speed, rather than size: The /Ox compiler option produces code that favors execution speed over smaller size. But in particular, the following