Here is ios_base::Init https://github.com/gcc-mirror/gcc/blob/master/libstdc%2B%2B-v3/include/std/iostream#L74 If you really want to understand what compiler put into your executable you have to disassemble it. Bear in mind that even if you knew whole source code of libstdc++ you would get different code in binary due to compiler optimizations and disabling them for final product is stupid unless they break something.
On June 3, 2017 8:35:43 AM GMT+02:00, bob by <blaoiwn4920...@gmail.com> wrote: >2017-06-03 5:26 GMT+04:00 Liu Hao <lh_mo...@126.com>: > >> On 2017/6/3 0:18, bob by wrote: >> >>> Can't find the code of std::ios_base::Init >>> >>> It should be somewhere in here, but I can't find it: >>> https://gcc.gnu.org/onlinedocs/gcc-6.3.0/libstdc++/api/a00801.html >>> >>> Why do you want to find its source? It is merely the answer to your >> previous question: `#include <iostream>` will make your executable >larger, >> although you seem not using anything in that header,. And jon_y is >right >> for the reason. > > >I want to understand what runtime is doing. I don't want the code I >can't >understand to be in my exe, it makes me feel like I don't understand >the >program I myself wrote. >------------------------------------------------------------------------------ >Check out the vibrant tech community on one of the world's most >engaging tech sites, Slashdot.org! http://sdm.link/slashdot >_______________________________________________ >Mingw-w64-public mailing list >Mingw-w64-public@lists.sourceforge.net >https://lists.sourceforge.net/lists/listinfo/mingw-w64-public ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Mingw-w64-public mailing list Mingw-w64-public@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
