We have integrated lots of C++ features in AvA, but it's inflexible to wrap all those features in C APIs for C specs. In this purpose, we decide to always generate C++ files for both C and C++ specs.
How has this been tested?
Tested with cudadrv spec.
Types of changes
[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Document update (this change is mainly a documentation update)
Checklist:
[x] My code passes format and lint checks.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[x] I have commented my code, particularly in hard-to-understand areas.
[x] My changes generate no new warnings.
[x] I have tested my code with a reasonable workload.
Description
We have integrated lots of C++ features in AvA, but it's inflexible to wrap all those features in C APIs for C specs. In this purpose, we decide to always generate C++ files for both C and C++ specs.
How has this been tested?
Tested with cudadrv spec.
Types of changes
Checklist: