Run ast dump twice with implicit includes defined and not defined. This increases coverage as some systems require them, others will fail with them.
Details
Details
Diff Detail
Diff Detail
- Repository
- rG LLVM Github Monorepo
Event Timeline
Comment Actions
The old impl for me was resulting in these kinds of errors during parsing.
/usr/include/c++/10/cstdint:52:11: error: no member named 'int_fast8_t' in the global namespace using ::int_fast8_t; ~~^
After removing the implicit includes, these errors went away and generation completed as intended.
Comment Actions
Run 2 invocations, one with implicit includes, one without them. If either has no errors the json will be generated, otherwise an empty implementation will be emitted.
Some systems seem to require the implicit includes, others, including mine, will fail with them defined.
Comment Actions
Instead of running it twice, it would be better if we understood better what the problem is.
I can't reproduce any problem with the implicit includes present. Can you reduce the code being compiled by the tool to find out why their presence causes a problem?