oiaohm wrote: > cross complier build bug has existed for ages in gcc. Profile building requires running the exe and monitoring the outcomes. > > You will find that MSYS runs faster inside wine than on Windows. > > This is another major problem with profile building inside wine. Wine has a different profile shape to real windows. > > It would be really nice if gcc could support profiling in a virtual machine simply or emulators. Currently its a trip threw manual hell. > > Since the only reason profiled bootstrap fails is that the test executable to generate the gmon.out fails. What makes this bad is gcc default build scripts don't include away of declaring run binary?s produced with the following out hacking the make files. Yes it can be made work with a lot of makefile editing. > > But be warned binfmt_misc is generally not a recommend prac by us. Because in our eyes it makes it too simple to run a exe as root. If you proceed to go this path. > > rubenvb also depending on the version gcc you are building. Gcc 4.6 using link time optimization the difference between profiled and not is a lot smaller than 10 to 15 percent. Avoids the build profile step. > > Profiled major gains was mostly because of lack of link time optimization. Ah ok. I figured as much, but if there's no gain to be had, I won't put any more time into it. Thanks for the help!
