From: Deruupu Sutoomo <phdofthehouse@gmail.com>
To: gcc@gcc.gnu.org
Subject: [ Plugins ] Read-only, or...?
Date: Mon, 12 Mar 2018 14:47:00 -0000 [thread overview]
Message-ID: <CANHA4OgHBCx5yvvCrr=AZqejLchTgmnAhdCnsWKo47xtc56x7g@mail.gmail.com> (raw)
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?
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! )
next reply other threads:[~2018-03-12 14:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-12 14:47 Deruupu Sutoomo [this message]
2018-03-12 18:15 ` Richard Biener
2018-03-12 20:13 ` Deruupu Sutoomo
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CANHA4OgHBCx5yvvCrr=AZqejLchTgmnAhdCnsWKo47xtc56x7g@mail.gmail.com' \
--to=phdofthehouse@gmail.com \
--cc=gcc@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).