From: Polyvios P. <pol...@cs...> - 2007-03-19 18:35:44
|
Hello, I am trying to use the current CIL (latest from svn) to parse files that were generated by the CIL 1.3.2 merger. I'm having a problem compiling them which distills down to the following example: static int f__extinline(); static int f__extinline() { return 0; } gcc accepts this code, whereas CIL doesn't. I read the __extinline entry in the "known bugs" documentation section, but it doesn't seem like CIL should not even accept the code. I'm find with silently ignoring all but the first definition of the __extinline function, but here we have a declaration and a definition so it should be straightforward. Is that a bug? Should I go rename all __extinline functions created by CIL 1.3.2 in my input sources by hand? thanks, -polyvios |
From: Mark K. <m.k...@cs...> - 2007-03-30 12:16:18
|
Hello again, I am thinking of starting to implement a tool which uses the output of CIL as its input. As I am not planning to write this tool in ocaml (but rather in c or c++) I do not think I can use the AST data within CIL directly, without some significant effort. Therefore I was thinking about writing a parser for the output of CIL using a parser generator. Obviously there are c grammars around that I could use, but I'd rather have something directly aimed for CIL output. Does anyone know of anyone who has attempted a similar setup, or does anyone have a grammar description (something more informative than the CIL API?). My apologies for asking this question again, it would just be really helpful to have a means of working with CIL without having to make my tool in ocaml. Kind regards, Mark |