aboutsummaryrefslogtreecommitdiff
path: root/llvm/lib/Target/WebAssembly/WebAssemblyRegStackify.cpp
diff options
context:
space:
mode:
authorSerge Pavlov <sepavloff@gmail.com>2022-10-20 12:24:50 +0700
committerSerge Pavlov <sepavloff@gmail.com>2022-11-16 13:32:27 +0700
commit1f67dc8b7c225290d1b3eb93d90e2c9861aeefc0 (patch)
treef643b44b93e3fdb6ec8d9809e2ebeaea75cdf6be /llvm/lib/Target/WebAssembly/WebAssemblyRegStackify.cpp
parentfde4ef19737e142fbe2fe2a3edd31963a254d3dd (diff)
downloadllvm-1f67dc8b7c225290d1b3eb93d90e2c9861aeefc0.zip
llvm-1f67dc8b7c225290d1b3eb93d90e2c9861aeefc0.tar.gz
llvm-1f67dc8b7c225290d1b3eb93d90e2c9861aeefc0.tar.bz2
[Driver] Enable nested configuration files
Users may partition parameters specified by configuration file and put different groups into separate files. These files are inserted into the main file using constructs `@file`. Relative file names in it are resolved relative to the including configuration file and this is not convenient in some cases. A configuration file, which resides in system directory, may need to include a file with user-defined parameters and still provide default definitions if such file is absent. To solve such problems, the option `--config=` is allowed inside configuration files. Like `@file` it results in insertion of command-line arguments but the algorithm of file search is different and allows overriding system definitions with user ones. Differential Revision: https://reviews.llvm.org/D136354
Diffstat (limited to 'llvm/lib/Target/WebAssembly/WebAssemblyRegStackify.cpp')
0 files changed, 0 insertions, 0 deletions