* gengtype and automatically generated files
@ 2021-01-04 17:40 Bill Schmidt
2021-01-04 19:36 ` Jeff Law
2021-01-04 19:45 ` Bill Schmidt
0 siblings, 2 replies; 4+ messages in thread
From: Bill Schmidt @ 2021-01-04 17:40 UTC (permalink / raw)
To: gcc
Hi! I'm attempting to do something that may not have been done before,
so I'm looking for advice, or a pointer to where, in fact, it has been
done before. :)
I'm automatically generating a back-end header file that declares some
structures that include trees, and a bunch of global variables that are
also trees. I've marked everything up appropriately, but I also need to
teach the garbage collector that this file exists.
Most back-end files are automatically scanned by gengtype. Per the
documentation, anything that isn't handled automatically needs to be
added to target_gtfiles in config.gcc. However, I can't come up with a
syntax for describing a file in the gcc/ build subdirectory. Some
places in config.gcc allow "./filename" as shorthand for "filename"
being in the current build directory, but that doesn't seem to work for
adding something to gtyp-input.list.
Any recommendations on what I should do next? At the moment it looks
like I might have to hack on gengtype to invent a way to scan a file in
the build directory, but I have a mild amount of hope that someone has
solved this before. Thanks for any help!
Bill
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: gengtype and automatically generated files
2021-01-04 17:40 gengtype and automatically generated files Bill Schmidt
@ 2021-01-04 19:36 ` Jeff Law
2021-01-05 21:41 ` Bill Schmidt
2021-01-04 19:45 ` Bill Schmidt
1 sibling, 1 reply; 4+ messages in thread
From: Jeff Law @ 2021-01-04 19:36 UTC (permalink / raw)
To: wschmidt, gcc
On 1/4/21 10:40 AM, Bill Schmidt via Gcc wrote:
> Hi! I'm attempting to do something that may not have been done
> before, so I'm looking for advice, or a pointer to where, in fact, it
> has been done before. :)
>
> I'm automatically generating a back-end header file that declares some
> structures that include trees, and a bunch of global variables that
> are also trees. I've marked everything up appropriately, but I also
> need to teach the garbage collector that this file exists.
>
> Most back-end files are automatically scanned by gengtype. Per the
> documentation, anything that isn't handled automatically needs to be
> added to target_gtfiles in config.gcc. However, I can't come up with
> a syntax for describing a file in the gcc/ build subdirectory. Some
> places in config.gcc allow "./filename" as shorthand for "filename"
> being in the current build directory, but that doesn't seem to work
> for adding something to gtyp-input.list.
>
> Any recommendations on what I should do next? At the moment it looks
> like I might have to hack on gengtype to invent a way to scan a file
> in the build directory, but I have a mild amount of hope that someone
> has solved this before. Thanks for any help!
Yea, I don't see any indication this has ever been done before. I'm a
bit surprised that ./<filename> doesn't work since gengtype runs from
the build directory and has to reference things in the source directory
and ./<whatever> would seem to naturally reference the build directory
Jeff
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: gengtype and automatically generated files
2021-01-04 17:40 gengtype and automatically generated files Bill Schmidt
2021-01-04 19:36 ` Jeff Law
@ 2021-01-04 19:45 ` Bill Schmidt
1 sibling, 0 replies; 4+ messages in thread
From: Bill Schmidt @ 2021-01-04 19:45 UTC (permalink / raw)
To: gcc
Actually, the "./filename" syntax works fine. I was missing a
dependency in my t-rs6000 to make the header file appear available.
Sorry for the noise!
Bill
On 1/4/21 11:40 AM, Bill Schmidt wrote:
> Hi! I'm attempting to do something that may not have been done before,
> so I'm looking for advice, or a pointer to where, in fact, it has been
> done before. :)
>
> I'm automatically generating a back-end header file that declares some
> structures that include trees, and a bunch of global variables that
> are also trees. I've marked everything up appropriately, but I also
> need to teach the garbage collector that this file exists.
>
> Most back-end files are automatically scanned by gengtype. Per the
> documentation, anything that isn't handled automatically needs to be
> added to target_gtfiles in config.gcc. However, I can't come up with
> a syntax for describing a file in the gcc/ build subdirectory. Some
> places in config.gcc allow "./filename" as shorthand for "filename"
> being in the current build directory, but that doesn't seem to work
> for adding something to gtyp-input.list.
>
> Any recommendations on what I should do next? At the moment it looks
> like I might have to hack on gengtype to invent a way to scan a file
> in the build directory, but I have a mild amount of hope that someone
> has solved this before. Thanks for any help!
>
> Bill
>
>
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: gengtype and automatically generated files
2021-01-04 19:36 ` Jeff Law
@ 2021-01-05 21:41 ` Bill Schmidt
0 siblings, 0 replies; 4+ messages in thread
From: Bill Schmidt @ 2021-01-05 21:41 UTC (permalink / raw)
To: Jeff Law, gcc
On 1/4/21 1:36 PM, Jeff Law wrote:
>
> On 1/4/21 10:40 AM, Bill Schmidt via Gcc wrote:
>> Hi! I'm attempting to do something that may not have been done
>> before, so I'm looking for advice, or a pointer to where, in fact, it
>> has been done before. :)
>>
>> I'm automatically generating a back-end header file that declares some
>> structures that include trees, and a bunch of global variables that
>> are also trees. I've marked everything up appropriately, but I also
>> need to teach the garbage collector that this file exists.
>>
>> Most back-end files are automatically scanned by gengtype. Per the
>> documentation, anything that isn't handled automatically needs to be
>> added to target_gtfiles in config.gcc. However, I can't come up with
>> a syntax for describing a file in the gcc/ build subdirectory. Some
>> places in config.gcc allow "./filename" as shorthand for "filename"
>> being in the current build directory, but that doesn't seem to work
>> for adding something to gtyp-input.list.
>>
>> Any recommendations on what I should do next? At the moment it looks
>> like I might have to hack on gengtype to invent a way to scan a file
>> in the build directory, but I have a mild amount of hope that someone
>> has solved this before. Thanks for any help!
> Yea, I don't see any indication this has ever been done before. I'm a
> bit surprised that ./<filename> doesn't work since gengtype runs from
> the build directory and has to reference things in the source directory
> and ./<whatever> would seem to naturally reference the build directory
>
> Jeff
>
I've gotten this working, with a little hacking on gengtype needed.
I'll propose that patch next stage 1.
Bill
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2021-01-05 21:41 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2021-01-04 17:40 gengtype and automatically generated files Bill Schmidt
2021-01-04 19:36 ` Jeff Law
2021-01-05 21:41 ` Bill Schmidt
2021-01-04 19:45 ` Bill Schmidt
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).