|
Revision tags: llvmorg-21-init, llvmorg-19.1.7, llvmorg-19.1.6, llvmorg-19.1.5, llvmorg-19.1.4, llvmorg-19.1.3 |
|
| #
e36b22f3 |
| 16-Oct-2024 |
Howard Roark <howard.roark@huawei-partners.com> |
Revert "[PGO] Preserve analysis results when nothing was instrumented (#93421)"
This reverts commit 23c64beeccc03c6a8329314ecd75864e09bb6d97.
|
|
Revision tags: llvmorg-19.1.2 |
|
| #
23c64bee |
| 12-Oct-2024 |
Pavel Samolysov <samolisov@gmail.com> |
[PGO] Preserve analysis results when nothing was instrumented (#93421)
The `PGOInstrumentationGen` pass should preserve all analysis results
when nothing was actually instrumented. Currently, only
[PGO] Preserve analysis results when nothing was instrumented (#93421)
The `PGOInstrumentationGen` pass should preserve all analysis results
when nothing was actually instrumented. Currently, only modules that
contain at least a single function definition are instrumented. When a
module contains only function declarations and, optionally, global
variable definitions (a module for the regular-LTO phase for thin-LTO
when LTOUnit splitting is enabled, for example), such module is not
instrumented (yet?) and there is no reason to invalidate any analysis
results.
NFC.
show more ...
|
|
Revision tags: llvmorg-19.1.1, llvmorg-19.1.0 |
|
| #
52b48a70 |
| 13-Sep-2024 |
JOE1994 <joseph942010@gmail.com> |
[llvm][unittests] Strip unneeded use of raw_string_ostream::str() (NFC)
Avoid excess layer of indirection.
|
|
Revision tags: llvmorg-19.1.0-rc4, llvmorg-19.1.0-rc3 |
|
| #
16e22a6d |
| 14-Aug-2024 |
Snehasish Kumar <snehasishk@google.com> |
Remove unused using decl and var in PGOInstrumentationTest (#103447)
|
|
Revision tags: llvmorg-19.1.0-rc2, llvmorg-19.1.0-rc1, llvmorg-20-init, llvmorg-18.1.8, llvmorg-18.1.7 |
|
| #
8c33b338 |
| 30-May-2024 |
Pavel Samolysov <samolisov@gmail.com> |
[PGO] Add a unit test for the PGOInstrumentationGen pass (#93636)
The patch introduces the gmock-based unittest infrastructure for PGO
Instrumentation and adds some test cases to check whether the
[PGO] Add a unit test for the PGOInstrumentationGen pass (#93636)
The patch introduces the gmock-based unittest infrastructure for PGO
Instrumentation and adds some test cases to check whether the
instrumentation has taken place. The testing infrastructure for analysis
modules was borrowed from the LoopPassManagerTest unittest and
simplified a bit to handle module analysis passes only. Actually, we are
testing whether the result of a trivial analysis pass was invalidated by
the PGOInstrumentGen one: we exploit the fact the pass invalidates all
the analysis results after a module was instrumented.
NFC.
show more ...
|