public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Julian Lohuis" <jlohuis@uni-osnabrueck.de>
To: gcc-help@gcc.gnu.org,
	"Julian Lohuis (Julian Lohuis)" <jlohuis@uni-osnabrueck.de>
Subject: dynamically parse c++-code-snippets from a plugin and skipping included files
Date: Thu, 09 Jun 2022 20:23:42 +0200	[thread overview]
Message-ID: <bad7-62a23a80-19b-48532980@200374311> (raw)
In-Reply-To: <46d3-62a23500-6a7-643fe980@26385808>

Hello,

I am writing a plugin for the latest gcc (12.1).
The plugin needs to dynamically parse c++-code-snippets to tree objects so they can be inserted at a later stage during compilation.

Is there a way to call into the existing parser to generate a tree from a const char*, source_range or anything similar?
Secondly can I make gcc ignore a file after the PLUGIN_INCLUDE_FILE-event of that file is called?

Thanks,
Julian Lohuis

On Thursday, June 09, 2022 19:58 CEST, "Julian Lohuis" <jlohuis@uni-osnabrueck.de> wrote:

>


      reply	other threads:[~2022-06-09 18:23 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-09 17:58 dynamically parse c++-code-snipping " Julian Lohuis
2022-06-09 18:23 ` Julian Lohuis [this message]

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=bad7-62a23a80-19b-48532980@200374311 \
    --to=jlohuis@uni-osnabrueck.de \
    --cc=gcc-help@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).