------- Comment #46 from olga at il dot ibm dot com 2008-01-21 20:42 ------- (In reply to comment #45) > > Sorry pursuing this issue, but let me completely understand it: when you run > > *with* profiling, there are two compilations and two executions. If you > > compile > > first with: > > > > -O3 -fipa-type-escape -fwhole-program -combine -fprofile-generate > > w_prof_global_var.c > > > > and run the generated executable, is it fail or not? > Sorry for beeing unclear. If I have done the compilation in 32 bit mode (the > default in my config), the generated executable run fine. Then I can use the > generated info to compile with -fprofile-use in 64 bit mode (-m64). gcc does > not complain about this dirty trick (I have no idea if it is supposed to work) > and produces an executable that fails to run.
I do not know whether it's legal or not to use information collected by 32bits profiling for optimizations in 64bits, most likely it's not. But it's not what importent here. If you run the executable generated by: -O3 -fipa-type-escape -fwhole-program -combine -fprofile-generate w_prof_global_var.c -m64 is it fail or not? Olga -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=34483
