Re: [ Plugins ] Read-only, or...?

[Richard Biener <richard dot guenther at gmail dot com>]

On Mon, Mar 12, 2018 at 3:47 PM, Deruupu Sutoomo
<phdofthehouse@gmail.com> wrote:
> Hello! I have a question regarding Plugins...
>
> I implemented a small one as a test to get used to working with GIMPLE and
> basic blocks. I read the Plugin API page, the wiki, and followed a tutorial
> to get started. However, I seem to have hit a bit of a road block in
> actually modifying the output of the compiled program itself.
>
> Are plugins a "read-only" look at the compilation model? If I wanted to
> provide an implementation of an intrinsic or modify a C++-compiled
> Translation Unit in some fashion, are plugins what I should be looking at?

plugins are not restricted to introspection, you have full access to all
internal GCC functions so modifying the IL is possible.

It might be easier to actually patch GCC though.

Richard.

> Background: I am attempting to add a function which relies on "compiler
> magic" and the file system to pull data made available to the program,
> replacing every instance of that function with the appropriate
> implementation (the data is to be constexpr).
>
> ( This is my first time on the mailing list, after carefully reading the
> descriptions for the others and asking around, this seemed to be
> appropriate. Let em know if I have the wrong space! )