Introduce module file extensions to piggy-back data onto module files.

Description

Introduce module file extensions to piggy-back data onto module files.

Introduce the notion of a module file extension, which introduces
additional information into a module file at the time it is built that
can then be queried when the module file is read. Module file
extensions are identified by a block name (which must be unique to the
extension) and can write any bitstream records into their own
extension block within the module file. When a module file is loaded,
any extension blocks are matched up with module file extension
readers, that are per-module-file and are given access to the input
bitstream.

Note that module file extensions can only be introduced by
programmatic clients that have access to the CompilerInvocation. There
is only one such extension at the moment, which is used for testing
the module file extension harness. As a future direction, one could
imagine allowing the plugin mechanism to introduce new module file
extensions.

Details

Auditors
martell
Committed
dgregorNov 3 2015, 10:33 AM
Parents
rL251954: Fix flakyness in TestWatchLocationWithWatchSet
Branches
Unknown
Tags
Unknown
martell raised a concern with this commit.Nov 3 2015, 12:38 PM
martell added a subscriber: martell.

Getting compile errors on windows host with this commit

/lib/Frontend/TestModuleFileExtension.cpp:69:15: error: ‘stderr’ was not declared in this scope
and
/lib/Frontend/TestModuleFileExtension.cpp:70:36: error: ‘fprintf’ was not declared in this scope

martell resigned from this audit.Nov 25 2015, 7:55 PM
martell removed a subscriber: martell.

Was fixed on HEAD after