[all-commits] [llvm/llvm-project] edbd9d: [X86] Check if there is stack access in the spille...

[weiguozhi via All-commits]

  Branch: refs/heads/main
  Home:   https://github.com/llvm/llvm-project
  Commit: edbd9d10bfb2c716fd8c38133f4a20ca7138fc90
      https://github.com/llvm/llvm-project/commit/edbd9d10bfb2c716fd8c38133f4a20ca7138fc90
  Author: weiguozhi <57237827+weiguozhi at users.noreply.github.com>
  Date:   2024-08-27 (Tue, 27 Aug 2024)

  Changed paths:
    M llvm/lib/Target/X86/X86FrameLowering.cpp
    M llvm/lib/Target/X86/X86FrameLowering.h
    M llvm/test/CodeGen/X86/avx512-intel-ocl.ll
    M llvm/test/CodeGen/X86/clobber_frame_ptr.ll
    A llvm/test/CodeGen/X86/clobber_frame_ptr2.ll
    M llvm/test/CodeGen/X86/x86-64-flags-intrinsics.ll

  Log Message:
  -----------
  [X86] Check if there is stack access in the spilled FP/BP range (#106035)

In the clobbered FP/BP range, we can't use it as normal FP/BP to access
stack. So if there are stack accesses due to register spill, scheduling
or other back end optimization, we should report an error instead of
silently generate wrong code.

Also try to minimize the save/restore range of the clobbered FP/BP if
the FrameSetup doesn't change stack size.



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