This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: BUILT_IN usage in tree-nested.c

From: Andrew Pinski <pinskia at physics dot uc dot edu>
To: kenner at vlsi1 dot ultra dot nyu dot edu (Richard Kenner)
Cc: gcc at gcc dot gnu dot org, rth at redhat dot com, Andrew Pinski <pinskia at physics dot uc dot edu>
Date: Sat, 5 Jun 2004 12:25:09 -0400
Subject: Re: BUILT_IN usage in tree-nested.c
References: <10406051619.AA23555@vlsi1.ultra.nyu.edu>

On Jun 5, 2004, at 12:19, Richard Kenner wrote:

A number of the tree-*.c files use the implicit_built_in_decls entries,
but, as far as I can see, only the C and C++ front-end initialize them
and it seems hard for other front ends to do so since the builtins
are stated in terms of C types.

How is this supposed to work?

I think you are supposed to initialize them in the front-end. gfortran initializes them in gfc_init_builtin_functions in fortran/f95-lang.c. Java initializes them in initialize_builtins in java/builtins.c.

Thanks,
Andrew Pinski

References:
- BUILT_IN usage in tree-nested.c
  - From: Richard Kenner

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]