[all-commits] [llvm/llvm-project] 6d12cf: Reapply "[IR][NFC] Drop vtable from PassConcept/Pa...

[Alexis Engelke via All-commits]

  Branch: refs/heads/main
  Home:   https://github.com/llvm/llvm-project
  Commit: 6d12cf1389fa3ef57f880b8c0b25e66f0caa2f32
      https://github.com/llvm/llvm-project/commit/6d12cf1389fa3ef57f880b8c0b25e66f0caa2f32
  Author: Alexis Engelke <engelke at in.tum.de>
  Date:   2026-07-14 (Tue, 14 Jul 2026)

  Changed paths:
    M llvm/include/llvm/Analysis/CGSCCPassManager.h
    M llvm/include/llvm/CodeGen/MachinePassManager.h
    M llvm/include/llvm/IR/PassManager.h
    M llvm/include/llvm/IR/PassManagerInternal.h
    M llvm/include/llvm/Transforms/Scalar/LoopPassManager.h

  Log Message:
  -----------
  Reapply "[IR][NFC] Drop vtable from PassConcept/PassModel" (#208168) (#209414)

The PassConcept/PassModel vtable has a size of 64 bytes (offset to top,
RTTI pointer, complete object destructor, deleting destructor, run,
printPipeline, name, isRequired), which add up to 53kiB (all
targets)/44 kiB (single-target). As more back-end passes get ported to
the new pass manager, this size will increase.

Remove the vtables by replacing the virtual dispatch with explicit
function pointers, initialized when adding the pass to the pass manager.
While this very slightly increases the cost of adding a pass, there's
also a very slight win from avoiding the vtable indirection when
running/destructing the pass.

Use a unique_ptr with a custom deleter to store PassConcept instances.
This avoids new/delete size mismatches.

This reverts commit 6ae5965f26e53d7338a779a73725a597a4d136e5.



To unsubscribe from these emails, change your notification settings at https://github.com/llvm/llvm-project/settings/notifications