From: Ian Molton <gcc_help-ian@mnementh.co.uk>
To: gcc-help@gcc.gnu.org
Subject: Re: RFC: AVR interrupt handling issue
Date: Sat, 18 Dec 2021 18:07:07 +0000 [thread overview]
Message-ID: <84ccbd9e-8738-f5b3-fefc-2b64b0cd9102@mnementh.co.uk> (raw)
In-Reply-To: <5093a413-50c3-14d0-7708-44f95f8d3dce@mnementh.co.uk>
Replying to myself for a moment - it would appear that
-fcall-used-reg="rXX" would do what I want (in theory), except for:
1) It doesnt appear to be documented much, or even work on AVR.
2) It applies to entire files, but I just want it to apply to one function.
Does anyone know if any work has been done in that direction? or is it
just abandoned?
-Ian
next prev parent reply other threads:[~2021-12-18 18:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-18 16:00 Ian Molton
2021-12-18 16:31 ` Henri Cloetens
2021-12-18 17:47 ` Ian Molton
2021-12-18 18:07 ` Ian Molton [this message]
2021-12-20 21:06 ` gcc not generating dwarf prologue_end and epilogue_begin .loc directives (was: Re: RFC: AVR interrupt handling issue) Ian Molton
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=84ccbd9e-8738-f5b3-fefc-2b64b0cd9102@mnementh.co.uk \
--to=gcc_help-ian@mnementh.co.uk \
--cc=gcc-help@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: 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).