riscv-gnu-toolchain/llvm.git - Unnamed repository; edit this file 'description' to name the repository.

Age	Commit message (Collapse)	Author	Files	Lines
2017-01-04	Fix for LLVM Bitcode API change (to use std::shared_ptr)	David Blaikie	1	-2/+2
	llvm-svn: 291018
2016-07-02	Use arrays or initializer lists to feed ArrayRefs instead of SmallVector ↵	Benjamin Kramer	1	-3/+1
	where possible. No functionality change intended llvm-svn: 274432
2015-12-08	Module file extensions: pass a Sema through to the extension writer.	Douglas Gregor	1	-0/+1
	Module file extensions are likely to need access to Sema/Preprocessor/ASTContext, and cannot get it through other sources. llvm-svn: 255065
2015-11-05	TestModuleFileExtension.cpp: Include <cstdio> explicitly for fprintf(3).	NAKAMURA Takumi	1	-0/+1
	llvm-svn: 252128
2015-11-03	Introduce module file extensions to piggy-back data onto module files.	Douglas Gregor	1	-0/+121
	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. llvm-svn: 251955