stacksize: hardcode some more frame sizes for __aeabi_* functions

These functions are defined in compiler-rt in assembly and therefore
don't have stack size information. However, they're often called so
these missing functions often inhibit stack size calculation.

Example, before:

    $ tinygo build -o test.elf -target=cortex-m-qemu -print-stacks ./testdata/float.go
    function                         stack usage (in bytes)
    Reset_Handler                    unknown, __aeabi_memclr does not have stack frame information
    runtime.run$1                    unknown, __aeabi_dcmpgt does not have stack frame information

After:

    $ tinygo build -o test.elf -target=cortex-m-qemu -print-stacks ./testdata/float.go
    function                         stack usage (in bytes)
    Reset_Handler                    260
    runtime.run$1                    224

stacksize/stacksize.go

@@ -201,7 +201,25 @@ func CallGraph(f *elf.File, callsIndirectFunction []string) (map[string][]*CallN
 	case elf.EM_ARM:
 		knownFrameSizes := map[string]uint64{
 			// implemented with assembly in compiler-rt
+			"__aeabi_idivmod":  3 * 4, // 3 registers on thumb1 but 1 register on thumb2
 			"__aeabi_uidivmod": 3 * 4, // 3 registers on thumb1 but 1 register on thumb2
+			"__aeabi_ldivmod":  2 * 4,
+			"__aeabi_uldivmod": 2 * 4,
+			"__aeabi_memclr":   2 * 4, // 2 registers on thumb1
+			"__aeabi_memset":   2 * 4, // 2 registers on thumb1
+			"__aeabi_memcmp":   2 * 4, // 2 registers on thumb1
+			"__aeabi_memcpy":   2 * 4, // 2 registers on thumb1
+			"__aeabi_memmove":  2 * 4, // 2 registers on thumb1
+			"__aeabi_dcmpeq":   2 * 4,
+			"__aeabi_dcmplt":   2 * 4,
+			"__aeabi_dcmple":   2 * 4,
+			"__aeabi_dcmpge":   2 * 4,
+			"__aeabi_dcmpgt":   2 * 4,
+			"__aeabi_fcmpeq":   2 * 4,
+			"__aeabi_fcmplt":   2 * 4,
+			"__aeabi_fcmple":   2 * 4,
+			"__aeabi_fcmpge":   2 * 4,
+			"__aeabi_fcmpgt":   2 * 4,
 		}
 		for name, size := range knownFrameSizes {
 			if sym, ok := symbolNames[name]; ok {