diff options
| author | Chuanqi Xu <yedeng.yd@linux.alibaba.com> | 2024-09-26 15:56:17 +0800 |
|---|---|---|
| committer | Chuanqi Xu <yedeng.yd@linux.alibaba.com> | 2024-09-26 15:59:02 +0800 |
| commit | e7569b30861cce7064fdc7b0e3ad1ee80fbc1fa7 (patch) | |
| tree | ed407c248ce6a7fc74056731a5afa99a2080863f /clang/lib/CodeGen/CodeGenModule.cpp | |
| parent | ae54a00cc1eb64a0300e190ccdc46ae9b31d2835 (diff) | |
| download | llvm-e7569b30861cce7064fdc7b0e3ad1ee80fbc1fa7.zip llvm-e7569b30861cce7064fdc7b0e3ad1ee80fbc1fa7.tar.gz llvm-e7569b30861cce7064fdc7b0e3ad1ee80fbc1fa7.tar.bz2 | |
[clang] [Modules] Don't assume an overriden module file can not be out-of-date
There is an assertion in ModuleFile assumes that an overriden module
file can't be out of date. But it is not seriously true in the case
clangd. e.g., the source files are overriden, but clangd relies on if
the files are out of date to trigger rebuilding preamble.
And techniquely, overriden doesn't imply it can't be out of date. This
was found during the use clangd of a large code base with modules.
Although I failed to reproduce an example, I feel it is fine to land
this directly for this particular case.
Diffstat (limited to 'clang/lib/CodeGen/CodeGenModule.cpp')
0 files changed, 0 insertions, 0 deletions