So Fordy it really translates to an actual CALL or JMP in assembly? Interesting.
IMO C++ translates into an awful lot of jumping and calling which all of us asm programmers know is bad. How do they optimize this - especially with virtual classes and functions?
As far as I know.....I know if you follow through in debug mode you see the call...but then I guess it may be a different story for release mode......Originally posted by Bubba
So Fordy it really translates to an actual CALL or JMP in assembly? Interesting.
I suppose a lot of this depends on the code....use of inline can make a big difference if used properly (with all those operator overloads), and the compiler has a fair amount of leeway when it's optomising.Originally posted by Bubba
IMO C++ translates into an awful lot of jumping and calling which all of us asm programmers know is bad. How do they optimize this - especially with virtual classes and functions?
Also, when you see all those calls in your dissasembly, is it from following a debug build? If so, you may find a lot of those calls dissapear in release mode because compilers may disable inlining for debug builds
Very interesting. However, I think we've gone beyond the scope of this thread....again.
I do that all the time. Sorry guys.
