changeset 332:73c528d2cd4d

- todo and changelog update
author Tassilo Philipp
date Sat, 23 Nov 2019 13:53:28 +0100
parents 74c056b597b7
children 4e9d3cb9870f
files ChangeLog ToDo
diffstat 2 files changed, 6 insertions(+), 0 deletions(-) [+]
line wrap: on
line diff
--- a/ChangeLog	Sat Nov 23 13:51:35 2019 +0100
+++ b/ChangeLog	Sat Nov 23 13:53:28 2019 +0100
@@ -15,8 +15,13 @@
   o dlGetLibraryPath() now accepts NULL as argument to return path to executable
 doc:
   o more detail in support matrix for bi-endian platforms
+  o improvements/corrections to calling convention appendix
+  o PPC64 calling convention description
+  o man page additions for clarity
 tests:
   o dynload_plain test extended to test UTF-8 library paths
+  o better output for plain test
+  o better output and *nix fix for plain_c++ test
 buildsys:
   o default ./configure: FreeBSD/mips*hf needed -mhard-float compiler flag set explicitly
   o better MacOS Mojave support in ./configure (Mojave dropped i386 builds)
--- a/ToDo	Sat Nov 23 13:51:35 2019 +0100
+++ b/ToDo	Sat Nov 23 13:53:28 2019 +0100
@@ -135,6 +135,7 @@
 - introduce doc overview tables and common vocab for calling convention specifics, following example of table on page 13 of https://www.linux-mips.org/pub/linux/mips/doc/ABI/MIPS-N32-ABI-Handbook.pdf; also as inspiration, e.g. user 'preserved' instead of 'permanent', etc. https://developer.apple.com/library/content/documentation/Xcode/Conceptual/iPhoneOSABIReference/Articles/ARMv6FunctionCallingConventions.html#//apple_ref/doc/uid/TP40009021-SW4
   * also, get inspiration for naming for GCC predefs as talked about in https://stffrdhrn.github.io/software/embedded/openrisc/2018/06/08/gcc_stack_frames.html
 - make stack layout diagrams better, e.g. add grow direction (example: https://developer.apple.com/library/content/documentation/Xcode/Conceptual/iPhoneOSABIReference/art/arm_stack.jpg on https://developer.apple.com/library/content/documentation/Xcode/Conceptual/iPhoneOSABIReference/Articles/ARMv6FunctionCallingConventions.html#//apple_ref/doc/uid/TP40009021-SW1)
+  * another example, chapter 3 of: ftp://www.sourceware.org/pub/binutils/ppc-docs/ppc-poweropen/
 - provide more examples on how to use dyncall, dynload and dyncallback
   * e.g. enhance manual with a couple of examples (e.g. calling MessageBoxA on windows, etc.)
 - manuals for bindings (as stated in bindings-section, above)