I included the system.h file, but I still get the same errors. I think ive gotten something really wrong.. The developer of the extension module seems to be out of touch with it. I was wondering if someone has used it before and could help me with what all should be include in the Makefile of the module to get the compilation succeed. I am a novice and have not worked with gcc code before. I am trying to learn through the extension module, simple instrumentations to the gcc code. I need to do this for a project to instrument gcc to provide runtime bounds checking.. Could you please advise if I can use the GCC Plug-in feature to do this instead ? And if so, where can I get a patch for GCC to support plug-ins and libraries/headers etc I will need to link the plug-in code for compilation ? Many Thanks, Aravinda On Tue, Apr 7, 2009 at 12:54 AM, Ian Lance Taylor <iant@xxxxxxxxxx> wrote: > Aravinda <aravindakidambi@xxxxxxxxx> writes: > >> I am trying to compile a GCC Extension module to do a simple AST walk >> using the gem_finish_function hook. > > Extension modules are not supported by the standard FSF release of gcc. > You may do better to ask whomever wrote the extension module support. > >> I have all the necessary header >> files and object files included for compiling the module as far as I >> know. However I still get several errors for all declarations in gcc >> header files which include either a 'bool' type or 'HOST_WIDE_INT' >> type or the 'ENUM_BITFIELD' type. I get the following errors for all >> variables declared using one of the three.. >> >> gcc-4.3.0/gcc/double-int.h:121: error: expected declaration specifiers >> or ‘...’ before ‘bool’ >> /gcc-4.3.0/gcc/tree.h:3982: error: expected declaration specifiers or >> ‘...’ before ‘HOST_WIDE_INT’ >> /gcc-4.3.0/gcc/tree.h:3351: error: expected specifier-qualifier-list >> before ‘ENUM_BITFIELD’ >> >> etc.. >> Im not sure what I am missing and why it cannot understand these >> types. Please suggest how or what I need to include in my module to >> fix these errors. > > These are all defined in system.h. Perhaps you should #include that. > > Ian >
