This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: targetm.init_builtins and build_common_builtin_nodes ordering
- From: Richard Guenther <richard dot guenther at gmail dot com>
- To: Mike Stump <mikestump at comcast dot net>
- Cc: GCC Development <gcc at gcc dot gnu dot org>, Jack Howarth <howarth at bromo dot med dot uc dot edu>
- Date: Mon, 7 Feb 2011 11:51:55 +0100
- Subject: Re: targetm.init_builtins and build_common_builtin_nodes ordering
- References: <32053408-BCA3-4BA7-A968-90D73DFDF998@comcast.net>
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.