llvm-project.git/llvm/lib/CodeGen/RegAllocEvictionAdvisor.cpp, branch users/nico/python-1

[CodeGen][NewPM] Port RegAllocPriorityAdvisor analysis to NPM (#118462)

2025-02-20T04:05:49+00:00

Similar to #117309.

The advisor and logger are accessed through the provider, which is
served by the new PM. Legacy PM forwards calls to the provider.
New PM is a machine function analysis that lazily initializes the
provider.

[CodeGen][NewPM] Port RegAllocEvictionAdvisor analysis to NPM (#117309)

2025-02-18T11:55:06+00:00

Legacy pass used to provide the advisor, so this extracts that logic
into a provider class used by both analysis passes.

All three (Default, Release, Development) legacy passes
`*AdvisorAnalysis` are basically renamed to `*AdvisorProvider`, so the
actual legacy wrapper passes are `*AdvisorAnalysisLegacy`.

There is only one NPM analysis `RegAllocEvictionAnalysis` that switches
between the three providers in the `::run` method, to be cached by the
NPM.

Also adds `RequireAnalysis` to the optimized
target reg alloc codegen builder.

[RegAlloc] Remove redundant prints of LiveInterval weight. (#116451)

2024-11-16T00:43:30+00:00

LiveInterval::print has included the weight since early 2018. We don't
need to print again after we print the interval.

[IR] Don't include Module.h in Analysis.h (NFC) (#97023)

2024-06-28T12:30:47+00:00

Replace it with a forward declaration instead. Analysis.h is pulled in
by all passes, but not all passes need to access the module.

Fix error message when regalloc eviction advisor analysis could not be created (#72165)

2023-11-14T19:17:17+00:00

[MC] Add MCRegisterInfo::regunits for iteration over register units

2023-06-16T02:39:50+00:00

Reviewed By: foad

Differential Revision: https://reviews.llvm.org/D152098

Move global namespace cl::opt inside llvm::

2023-02-14T08:09:44+00:00

Reland "[mlgo] Hook up the interactive runner to the mlgo-ed passes"

2023-02-04T01:54:42+00:00

This reverts commit a772f0bb920a4957fb94dd8dbe45943809fd0ec3.

The main problem was related to how we handled `dbgs()` from the hosted
compiler. Using explicit `subprocess.communicate`, and not relying on
dbgs() being flushed until the end appears to address the problem.

Also some fixes due to some bots running older pythons, so we can't have
nice things like `int | float` and such.

Revert "[mlgo] Hook up the interactive runner to the mlgo-ed passes"

2023-02-04T00:34:31+00:00

This reverts commit a7354899d1a235a796b3a2ccb45f6596983c8672.

The way stdout/stderr get routed seems to work differently locally and
on the bots. Investigating.

[mlgo] Hook up the interactive runner to the mlgo-ed passes

2023-02-04T00:22:57+00:00

This hooks up the interactive model runner to the passes that support
ml-based decisions. Because the interface to this runner is the exact
same as the one used during inference, we just reuse the exact same
setup we have for "release mode". This makes "release mode" a misnomer -
and that's something we needed to resolve sooner or later (e.g.
supporting more than one embedded model for the same problem was another
reason to drop that nomenclature). That will happen in a subsequent
change.

To use this evaluator, just enable the pass in (currently) "release"
mode, but also pass the base name for the 2 channel files via the
pass-specific flag.

The 2 files are the responsibilty of the hosting process. The added
tests use a minimal, toy such host, illustrating setup and
communication.

Differential Revision: https://reviews.llvm.org/D143218