According to this article gcc uses several intermediate formats before generating code. I read that the GIMPLE format uses three address code, which seems to be the easiest intermediate language to use. But I need some more detail, as I need to build a tool that can take the intermediate code and insert some code to it before generating the final code.
For this I first need to know how can I even generate the GIMPLE format code and save it in a file. So I'm looking for some documents and examples. Also, if anyone has worked with such things, can I know the complexity of this task, which is to insert some code into the intermediate code?
You might find it easier to write a plugin for GCC, which would allow you to hook the GIMPLE generation and alter it inside GCC, which should drop the downtime of saving, editing then trying to compile from GIMPLE form. MELT is one such plugin (though it offers way more than just altering the lower level representations). There is also a nice PDF here on GIMPLE altering plugins.
Else, you can look here for information on how GCC's GIMPLE works. In terms of dumping GIMPLE out:
You can request to dump a C-like representation of the GIMPLE form with the flag -fdump-tree-gimple.
You can easily generate GIMPLE representation of any file using the flag -fdump-tree-gimple.
If you want to write a plugin, then you might be interested in how passes work on GCC. You can see the output of each pass with flags of the form:
-fdump-<ir>-<passname>
where ir could be:
tree: Intraprocedural passes on GIMPLEipa: Interprocedural passes on GIMPLErtl: Intraprocedural passes on RTL
Use <passname> = all to see all the dumps, e.g. -fdump-ipa-all.
I tried the flag -fdump-tree-gimple. It works only for the C/C++ language, and not for other languages such as Java, Ada, Fortran, and Objective-C)
来源：https://stackoverflow.com/questions/9099391/playing-with-gccs-intermediate-gimple-format