public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Gary Oblock <goblock@marvell.com>
To: GCC Development <gcc@gcc.gnu.org>
Subject: How can I build new functions on the fly during optimization?
Date: Thu, 19 Sep 2019 02:27:00 -0000	[thread overview]
Message-ID: <MWHPR18MB107260B21DB2BBD8DA1CD726B9890@MWHPR18MB1072.namprd18.prod.outlook.com> (raw)

I'm trying to build new functions on the fly during optimization.
For those of you that have not been following my previous questions,
this is structure reorganization optimization related. For example when
somebody frees an array of type fu, I'd like to build a new
function _reorg_free_fu which does the correct things for a
transformed array of type _reorg_fu.

I've run across uses of these:
  build_fn_decl
  gimple_build_call
However, I don't see any code going any further than that.

Anybody have any ideas about how I can accomplish the rest of
what I need to do? Note, I'll be doing this during LTRANS.

Thanks,

Gary Oblock

             reply	other threads:[~2019-09-19  2:27 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-19  2:27 Gary Oblock [this message]
2019-09-19 10:51 ` Richard Biener

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=MWHPR18MB107260B21DB2BBD8DA1CD726B9890@MWHPR18MB1072.namprd18.prod.outlook.com \
    --to=goblock@marvell.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).