gcc-python-plugin May 2013

gcc-python-plugin@lists.stg.fedorahosted.org

4 participants
3 discussions

global vs global static in c/c++ AST representation
by gcc frickler 23 May '13

23 May '13

Hi, does anybody know how to distinguish a global from a global static variable? eg. int glob; static int moduleGlob; void f() {static int inner;} All of them go into the bss segment but the static int moduleGlob is exported with a mangled name to a .so (so it doesn't conflict at link time) from https://gcc-python-plugin.readthedocs.org/en/latest/working-with-c.html#fin… i got: for var in gcc.get_variables(): type_ = var.decl.type It does not seem to be a attribute of a VAR_DECL or anywhere near var, var.decl or var.decl.type the static predicate found on var.decl is just saying it goes in the bss segment (true in all of the above cases) and got nothing to do with the static keyword which just controls visibility on link time. At which pass should this be examined? Regards

1 0

Not able to execute examples - problem with libgcc-c-api.so
by Binkowski, Cassio 18 May '13

18 May '13

Hi all, I have recently built the plugin from source in a Fedora VM and, when I try to execute the examples, I get the following error: *[fedora@localhost gcc-python-plugin]$ ./gcc-with-python examples/show-gimple.py test.c cc1: error: cannot load plugin /home/fedora/Desktop/gcc-python-plugin/python.so libgcc-c-api.so: cannot open shared object file: No such file or directory* Seems like a problem with libgcc-c-api.so. However, libgcc seems to be up to date. Can you please help? Thanks Cassio PS: Is there a way to build it in MacOS?

2 4

Identifying global state within GCC
by David Malcolm 02 May '13

02 May '13

I had a go at writing a custom pass to try to locate places where GCC makes use of global state. You can see the pass here (which I implemented using gcc-python-plugin): https://gcc-python-plugin.readthedocs.org/en/latest/working-with-c.html#fin… A build log from recompiling gcc using this pass can be seen at: http://fedorapeople.org/~dmalcolm/gcc/2013-05-01/make.log (about 12MB in size; I killed it when I saw that stage 1 was done). I'm sure there are quite a few false positives in there. Hope this is helpful. FWIW I had an earlier version of the pass which merely gave *declaration* sites for global variables, rather than all *uses* of such variables. Dave

2 1

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

gcc-python-plugin May 2013