targetm.init_builtins and build_common_builtin_nodes ordering

[Jack Howarth]

On Mon, Feb 07, 2011 at 11:51:55AM +0100, Richard Guenther wrote:
> On Mon, Feb 7, 2011 at 2:35 AM, Mike Stump <mikestump@comcast.net> wrote:
> > So, in c-common.c we have:
> >
> >  targetm.init_builtins ();
> >  build_common_builtin_nodes ();
> >
> > and in f95-1.c we have:
> >
> >  build_common_builtin_nodes ();
> >  targetm.init_builtins ();
> 
> They are "unordered", thus, targetm.init_builtins is supposed to initialize
> target specific builtins only.
> 
> > I would like to change c-common.c to match fortran, so that the target hook can slightly alter (rename) the linkage name of some of the common builtin nodes.  If that answer is no, what's the best way to get __divdc3 renamed?
> 
> I would say add a new hook that can be called from build_common_builtin_nodes
> instead.

Richard,
   The workaround that Mike came up with for darwin is posted here...

http://gcc.gnu.org/ml/gcc-testresults/2011-02/msg00726.html

FYI, I tried inverting the order of targetm.init_builtins (); and build_common_builtin_nodes ();
in c-common.c to match that in f95-1.c but it broke the bootstrap.
       Jack

> 
> Richard.