public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "yann at poupet dot eu" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug rtl-optimization/55757] Suboptimal interrupt prologue/epilogue for ARMv7-M (Cortex-M3) Date: Tue, 28 Nov 2023 23:10:30 +0000 [thread overview] Message-ID: <bug-55757-4-POGxz8zpJ0@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-55757-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=55757 Yann Poupet <yann at poupet dot eu> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |yann at poupet dot eu --- Comment #8 from Yann Poupet <yann at poupet dot eu> --- Hi, I had the same issue and modified GCC so that the prologue/epilogue do not save/restore R4-R11 if it's not required - assuming these are caller-saved (same effect as -fcall-used-[r4...r11]), with a new function attribute. I'm not sure if this has a chance to be accepted upstream though. I'm using it in 2 cases: - ISR as described above - for the tasks launched by my own home made microkernel. Indeed, when the kernel starts a task starting its entry function, there's no need to save any register, it's just a waste of stack space. Anyone still interested with a solution ? The patch is very small, maybe 10 lines. Cheers Yann
prev parent reply other threads:[~2023-11-28 23:10 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-12-20 15:04 [Bug rtl-optimization/55757] New: " freddie_chopin at op dot pl 2012-12-20 15:24 ` [Bug rtl-optimization/55757] " freddie_chopin at op dot pl 2012-12-20 16:52 ` rearnsha at gcc dot gnu.org 2012-12-20 17:08 ` freddie_chopin at op dot pl 2012-12-21 3:23 ` joey.ye at arm dot com 2012-12-21 3:32 ` joey.ye at arm dot com 2012-12-21 7:09 ` freddie_chopin at op dot pl 2013-03-02 15:23 ` web at brolinembedded dot se 2023-11-28 23:10 ` yann at poupet dot eu [this message]
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=bug-55757-4-POGxz8zpJ0@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.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: linkBe 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).