[LLVMbugs] [Bug 1618] New: Frame moves information emitter should be refactored/ generalized

bugzilla-daemon at cs.uiuc.edu bugzilla-daemon at cs.uiuc.edu
Tue Aug 21 12:56:18 PDT 2007


           Summary: Frame moves information emitter should be
           Product: libraries
           Version: trunk
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: enhancement
          Priority: P2
         Component: Common Code Generator Code
        AssignedTo: unassignedbugs at nondot.org
        ReportedBy: asl at math.spbu.ru
                CC: llvmbugs at cs.uiuc.edu

Unwinding runtime and debugger needs to know some facts about stack frame
layout during the entry of function: position of return address (or, it can be
not on stack, but in some register), caller's stack and frame pointer values,
frame positions for call-clobbered registers, etc. Even more, this information
can be valid not in the entry of funciton, but few instructions later.

Current frame moves information infrastructure is pretty simple and thus code
used it became very messy and hackish (look into X86 target) and even signgle
change in codegen can break the whole stuff.

The requirements of the needed infrastructure should be investigated and code
should be modified. Maybe the can be solved via hooks from prologue/epilogue
emitter plus some target machine information, maybe via machineinst

Good source of ideas can be gcc.

Configure bugmail: http://llvm.org/bugs/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.

More information about the llvm-bugs mailing list