From: Tomasz Jankowski <tomcioj@gmail.com>
To: gcc-help@gcc.gnu.org
Subject: Extending GCC with new optimization
Date: Fri, 17 Aug 2012 08:38:00 -0000 [thread overview]
Message-ID: <CAMxYpJxCzs2qLzy2dhC2c9ak4o_YgFx_1Ywp-YHi0W9uD=KV+w@mail.gmail.com> (raw)
Hello,
For one of my projects at university I have to create specific
optimization for GCC (in general I have to find arithmetic operations
in basic blocks and modify them a bit). I have some idea about
compilation process etc. but i't more theoretical then practical
knowledge.
Now I'm slowly learning about GCC internals and as I see I can
"easily" solve my problem by writing plugin in C. On the other hand I
found MELT project. At the moment I'm in point in which I'm not sure
which path I should choose: write MELT extension or write plugin in C.
I can also mention that my target is GCC 4.5.
Actually I don't know how can I treat plugins support in GCC. It's
low-level infrastructure for projects like MELT or straight way to
write static optimization?
next reply other threads:[~2012-08-17 7:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-17 8:38 Tomasz Jankowski [this message]
2012-08-18 17:09 ` Ian Lance Taylor
2012-08-21 22:57 ` Tomasz Jankowski
2012-08-22 7:51 ` Ian Lance Taylor
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='CAMxYpJxCzs2qLzy2dhC2c9ak4o_YgFx_1Ywp-YHi0W9uD=KV+w@mail.gmail.com' \
--to=tomcioj@gmail.com \
--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).