targets: do not set stack size per board

The needed stack size is hard to determine by the compiler. It will try,
but will fail in many common cases. Therefore, the runtime will pick a
fixed stack size.

There is a tradeoff between avoiding stack overflows and wasting RAM.
This tradeoff depends on the application: some don't need large stack
sizes but do need a lot of memory, while others need deep stacks but
aren't so memory constrained. That's why I've added a flag to do this on
the command line: https://github.com/tinygo-org/tinygo/pull/3159

It may be reasonable to use a different stack size per chip, for example
chips with lots of RAM could default to a larger stack size. But I don't
think it's a good idea to do this per board.
This commit is contained in:
Ayke van Laethem
2022-09-28 16:05:02 +02:00
committed by Ron Evans
parent 5548b5999b
commit a62044d89b
5 changed files with 3 additions and 8 deletions
+1 -2
View File
@@ -3,6 +3,5 @@
"build-tags": ["atsame54_xpro"],
"serial": "usb",
"flash-method": "openocd",
"openocd-interface": "cmsis-dap",
"default-stack-size": 4096
"openocd-interface": "cmsis-dap"
}
+1 -2
View File
@@ -6,6 +6,5 @@
"flash-1200-bps-reset": "true",
"flash-method": "msd",
"msd-volume-name": "FTHRCANBOOT",
"msd-firmware-name": "firmware.uf2",
"default-stack-size": 4096
"msd-firmware-name": "firmware.uf2"
}
+1 -2
View File
@@ -7,6 +7,5 @@
"linkerscript": "targets/qtpy-rp2040.ld",
"extra-files": [
"targets/qtpy-rp2040-boot-stage2.S"
],
"default-stack-size": 4096
]
}
-1
View File
@@ -3,7 +3,6 @@
"build-tags": ["teensy40", "teensy", "mimxrt1062", "nxp"],
"serial": "uart",
"automatic-stack-size": false,
"default-stack-size": 4096,
"linkerscript": "targets/mimxrt1062-teensy40.ld",
"extra-files": [
"src/device/nxp/mimxrt1062.s",
-1
View File
@@ -3,7 +3,6 @@
"build-tags": ["teensy41", "teensy", "mimxrt1062", "nxp"],
"serial": "uart",
"automatic-stack-size": false,
"default-stack-size": 4096,
"linkerscript": "targets/mimxrt1062-teensy40.ld",
"extra-files": [
"src/device/nxp/mimxrt1062.s",