add some documentation links to the assembler needed for the UNO bridges
ceterum censeo: good old C-linkage interoperability would be much more robust, reliable and easier to maintain compared to the current UNO-bridges approach of emulating the behaviour of the individual compiler, linker, dylib, unwind, etc. environments and thus being extremely platform specific. What an incredible waste of energy for little (if any) gain. SCNR. (cherry picked from commit c9fe5d026f2081d493a198a33cf3b1d558166965) Conflicts: bridges/source/cpp_uno/gcc3_freebsd_x86-64/call.s Change-Id: I728bce449e8e56572f31b50fb1452d1c2f9d7fea
This commit is contained in:
parent
959b25bc15
commit
d77d01b84a
@ -73,6 +73,9 @@ privateSnippetExecutor:
|
||||
ret
|
||||
.LFE3:
|
||||
.size privateSnippetExecutor, .-privateSnippetExecutor
|
||||
# see http://refspecs.linuxfoundation.org/LSB_3.0.0/LSB-Core-generic/LSB-Core-generic/ehframechpt.html
|
||||
# for details of the .eh_frame, the "Common Information Entry" and "Frame Description Entry" formats
|
||||
# and http://mentorembedded.github.io/cxx-abi/exceptions.pdf for more info
|
||||
.section .eh_frame,"a",@progbits
|
||||
.Lframe1:
|
||||
.long .LECIE1-.LSCIE1
|
||||
|
Loading…
x
Reference in New Issue
Block a user