Firm Bugtracker - cparser
Viewing Issue Advanced Details
1 preprocessor feature always 2008-12-01 11:22 2016-01-03 03:28
administrator  
Matze  
low  
closed 0.9.8  
fixed  
none    
none  
0000001: No preprocessor
cparser does not have a complete preprocessor of its own yet. We have to use the gcc preprocessor. This makes us dependent on gcc and compilation slightly slower. Having an own preprocessor would be better.
Work on an own preprocessor is underway (preprocessor.c) but far from finished.
Issue History
2008-12-01 11:22 administrator New Issue
2008-12-01 11:24 administrator Summary No preprocessor yet => No preprocessor
2008-12-02 10:31 Matze Status new => assigned
2008-12-02 10:31 Matze Assigned To => Matze
2009-03-03 21:26 Matze Priority high => normal
2009-03-03 21:26 Matze version 0.9.7 => 0.9.8
2009-03-03 21:26 Matze View Status public => private
2010-08-16 14:02 Matze Priority normal => low
2012-09-28 12:53 Matze Note Added: 0000147
2013-09-17 07:07 Matze Note Added: 0000179
2013-09-17 07:07 Matze View Status private => public
2014-01-10 21:08 Matze Note Added: 0000200
2014-01-10 21:08 Matze Status assigned => resolved
2014-01-10 21:08 Matze Resolution open => fixed
2016-01-03 03:28 Matze Status resolved => closed

Notes
(0000147)
Matze   
2012-09-28 12:53   
there has been a considerable amount of work in cparser preproc branch. There are still some edge cases with macro expansion left though, before we can successfully preprocess the glibc headers...
(0000179)
Matze   
2013-09-17 07:07   
By now the preprocessor is fully able to parse glibc headers and the system headers on os/x and is considered feature complete.
However we did not enable it by default just yet (use --no-external-pp to enable it).
(0000200)
Matze   
2014-01-10 21:08   
We switched to the integrated preprocessor by default in b9495a169363db32d8c8b5cf40938081533e4c85.