From: Bernhard Krug <b.krug@elektronenpumpe.de>
To: newlib@sourceware.org
Subject: libc: arm: setjmp jmp_buf exagerated size
Date: Tue, 14 Feb 2023 23:47:23 +0100 [thread overview]
Message-ID: <D94205CA-1195-4F8C-9373-954C62F7DE8B@elektronenpumpe.de> (raw)
Hello,
using setjmp to implement eight coroutines on an ARM Cortex-M0+ the allocated size of .data escalates, in my example, from 476 bytes to 1444 bytes!
I think "libc: arm: fix setjmp abi non-conformance" shouldn't use jmp_buf made of 20 long long ints on a 32bit arm without fpu :D
Can the #ifndef device detection/decision tree from the setjmp asm/source file be also used in the headers to set reasonable sizes?
For my machine and use-case gcc emits asm copying ten registers (as expected) which would be rightly sized.
Thanks for your work and consideration :)
next reply other threads:[~2023-02-14 22:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-14 22:47 Bernhard Krug [this message]
2023-02-15 11:09 ` [PATCH] " Bernhard Krug
2023-02-15 15:56 ` Bernhard Krug
2023-02-15 16:05 ` Bernhard Krug
2023-02-15 16:12 ` Richard Earnshaw
2023-02-15 16:40 ` Bernhard Krug
2023-02-15 17:01 ` Richard Earnshaw
2023-02-15 17:14 ` Bernhard Krug
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=D94205CA-1195-4F8C-9373-954C62F7DE8B@elektronenpumpe.de \
--to=b.krug@elektronenpumpe.de \
--cc=newlib@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).