FreeRTOS Support Archive
The FreeRTOS support forum is used to obtain active support directly from Real
Time Engineers Ltd. In return for using our top quality software and services for
free, we request you play fair and do your bit to help others too! Sign up
to receive notifications of new support topics then help where you can.
This is a read only archive of threads posted to the FreeRTOS support forum.
The archive is updated every week, so will not always contain the very latest posts.
Use these archive pages to search previous posts. Use the Live FreeRTOS Forum
link to reply to a post, or start a new support thread.
[FreeRTOS Home] [Live FreeRTOS Forum] [FAQ] [Archive Top] [July 2007 Threads] Recommendation for stack sizesPosted by Dan on July 27, 2007 Would it be possible to change the 'unsigned portSHORT usStackDepth;' to 'unsigned portLONG ulStackDepth;' in struct tskTaskControlBlock? (and update the modified references)
First, yes, I did need a stack larger than 64k variables.
2nd, being a short causes some compilers to emit slightly more code than if the type were the natural integer size.
3rd, being a short in a structure opens up the possibilities for problems with structure packing (although not likely an issue with this structure yet).
Dan Searles
RE: Recommendation for stack sizesPosted by Richard on July 27, 2007 You have been busy! Thanks for your comments and suggestions.
The stack size used to be unsigned portBASE_TYPE, but this caused problems on some 8bit systems where the stack could not be greater than 0xff. Long was considered too wasteful on 8bitters (mainly because of its use in the TCB rather than just as a function parameter), so short became the compromise. FreeRTOS.org has come a long way since then however and finds most uses in the 32bit world.
Regards.
RE: Recommendation for stack sizesPosted by David Hawks on July 27, 2007 > FreeRTOS.org...finds most uses in the 32bit world.
Really? Wow. Please don't forget about all the 8-bitters though. I still agree that "long" is too wasteful. If you make any change, perhaps you should make it configurable.
Copyright (C) Amazon Web Services, Inc. or its affiliates. All rights reserved.
|