[all-commits] [llvm/llvm-project] edf80d: [LTO][Veclib] Fix vector library handling with LTO...

[Usha Gupta via All-commits]

  Branch: refs/heads/main
  Home:   https://github.com/llvm/llvm-project
  Commit: edf80dce39b3c9f731423c1a1da4f99cbf768e7c
      https://github.com/llvm/llvm-project/commit/edf80dce39b3c9f731423c1a1da4f99cbf768e7c
  Author: Usha Gupta <usha.gupta at arm.com>
  Date:   2025-12-09 (Tue, 09 Dec 2025)

  Changed paths:
    M llvm/lib/LTO/LTOBackend.cpp
    M llvm/lib/LTO/ThinLTOCodeGenerator.cpp
    M llvm/lib/LTO/UpdateCompilerUsed.cpp
    A llvm/test/LTO/AArch64/frem-scalable-veclib.ll
    A llvm/test/LTO/AArch64/veclib-armpl-lto.ll
    A llvm/test/LTO/AArch64/veclib-armpl-lto2.ll

  Log Message:
  -----------
  [LTO][Veclib] Fix vector library handling with LTO (#170638)

Commit #167996 moved VecLib into TargetOptions and ensured clang
properly sets it. However, some LTO backend code paths were still
creating _TargetLibraryInfoImpl_ without passing the VecLib parameter
from `TargetMachine::Options`.

This PR completes the fix by ensuring that:

_LTOBackend.cpp, ThinLTOCodeGenerator.cpp, UpdateCompilerUsed.cpp_ all
pass `TM->Options.VecLib` when constructing _TargetLibraryInfoImpl_.

Without this fix, vector library information (e.g., -fveclib=ArmPL)
would not be properly recognized during LTO optimization and code
generation, potentially causing incorrect optimizations or linker errors
when vector library functions are referenced.



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