Displaying 3 results from an estimated 3 matches for "maybe_copy_epilogue_insn".
2009 Sep 18
2
[LLVMdev] OT: intel darwin losing primary target status
...ate.
* function.c (prologue, epilogue, sibcall_epilogue): Remove.
(prologue_insn_hash, epilogue_insn_hash): New.
(free_after_compilation): Adjust freeing accordingly.
(record_insns): Create hash table if needed; push insns into
hash instead of array.
(maybe_copy_epilogue_insn): New.
(contains): Search hash table instead of array.
(sibcall_epilogue_contains): Remove.
(thread_prologue_and_epilogue_insns): Split eh_return insns
and mark them as epilogues.
(reposition_prologue_and_epilogue_notes): Rewrite epilogue
scanning in...
2009 Sep 18
0
[LLVMdev] OT: intel darwin losing primary target status
On Sep 18, 2009, at 10:43 AM, Jack Howarth wrote:
> On Fri, Sep 18, 2009 at 10:28:15AM -0700, Nick Kledzik wrote:
>> So, when these test cases are run, is the binary linked against /usr/
>> lib/libgcc_s.10.5.dylib? or against some just built libgcc_s.
>> 10.5.dylib?
>> or against some just build libgcc_s.dylib? If either of the
>> latter, then
>> if you
2009 Sep 18
4
[LLVMdev] OT: intel darwin losing primary target status
On Fri, Sep 18, 2009 at 10:28:15AM -0700, Nick Kledzik wrote:
> So, when these test cases are run, is the binary linked against /usr/
> lib/libgcc_s.10.5.dylib? or against some just built libgcc_s.10.5.dylib?
> or against some just build libgcc_s.dylib? If either of the latter, then
> if you changed the FSF build of libgcc_s for darwin to have the right
> magic symbols, then