------- Comment #2 from jakub at gcc dot gnu dot org 2009-01-16 16:26 ------- Then that patch was wrong. You could have code compiled with gfortran 4.3 that references this symbol, which won't even start (e.g. with LD_BIND_NOW=1) against gcc 4.4 libgfortran. The symbol needs to be IMHO put back; if you really want and assembler supports .symver directive, it could be added as a __iso_c_binding_c_f_procpoin...@gfortran_1.0 which would prevent new code from linking against that symbol (which could screw up gfortran 4.3 linking against 4.4 libgfortran though).
-- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=38871