Steve Ellcey writes:
> On Tue, 2015-09-01 at 10:13 +0200, Georg-Johann Lay wrote:
>
> >
> > I'd have a look at what BEs are using non-default target_gtfiles.
> >
> > Johann
>
> There are a few BEs that add a .c file to target_gtfiles, but no
> platforms that add a .h file to target_gtfiles. I d
On Tue, 2015-09-01 at 10:13 +0200, Georg-Johann Lay wrote:
>
> I'd have a look at what BEs are using non-default target_gtfiles.
>
> Johann
There are a few BEs that add a .c file to target_gtfiles, but no
platforms that add a .h file to target_gtfiles. I do see a number
of platforms that defin
On Tue, 2015-09-01 at 08:11 +0100, Richard Sandiford wrote:
> config.gcc would need to add mips-private.h to target_gtfiles.
OK, that was what I missed.
> I'm not sure splitting the file is a good idea though. At the moment
> the definitions of all target hooks must be visible to a single TU.
>
Steve Ellcey schrieb:
I have a question about gengtype and GTY. I was looking at adding some
code to mips.c and it occurred to me that that file was getting very
large (19873 lines). So I wanted to add a new .c file instead but that
file needed some types that were defined in mips.c and not in
"Steve Ellcey " writes:
> I have a question about gengtype and GTY. I was looking at adding some
> code to mips.c and it occurred to me that that file was getting very
> large (19873 lines). So I wanted to add a new .c file instead but that
> file needed some types that were defined in mips.c an
I have a question about gengtype and GTY. I was looking at adding some
code to mips.c and it occurred to me that that file was getting very
large (19873 lines). So I wanted to add a new .c file instead but that
file needed some types that were defined in mips.c and not in a header file.
Specific
