From: "Fu, Chao-Ying" <fu@mips.com>
To: "Daniel Jacobowitz" <drow@false.org>
Cc: <gcc-patches@gcc.gnu.org>,
"Richard Sandiford" <rdsandiford@googlemail.com>,
<anemet@caviumnetworks.com>, <mark@codesourcery.com>,
"Lau, David" <davidlau@mips.com>
Subject: Re: [PATCH] MIPS function attributes for interrupt handlers
Date: Thu, 26 Feb 2009 09:48:00 -0000 [thread overview]
Message-ID: <000e01c997b7$706b4f60$a914a8c0@mips.com> (raw)
In-Reply-To: <20090225171443.GA19624@caradoc.them.org>
"Daniel Jacobowitz" wrote:
> On Tue, Feb 24, 2009 at 06:02:08PM -0800, Fu, Chao-Ying wrote:
> > Hi All,
> >
> > Based on the discussions last year, I will update my interrupt patch
to
> > support only the following
> > attributes.
> >
> > void __attribute__ ((interrupt )) v0 () { }
> > void __attribute__ ((interrupt (use_shadow_register_set))) v1 () { }
> > void __attribute__ ((interrupt (keep_interrupts_masked))) v2 () { }
> > void __attribute__ ((interrupt (use_shadow_register_set,
> > keep_interrupts_masked))) v3 () { }
>
> I have one question: does the patch cause GCC to generate eret? If
> so, is there another attribute needed for deret?
Yes, from the current patch GCC generates "eret" for return.
So, we may need another attribute as "use_debug_exception_return".
Thanks!
Regards,
Chao-ying
next prev parent reply other threads:[~2009-02-26 2:13 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-14 20:29 Fu, Chao-Ying
2008-10-15 23:47 ` Richard Sandiford
2008-10-20 23:03 ` Mark Mitchell
2008-10-20 23:24 ` Adam Nemet
2008-10-21 16:15 ` Weddington, Eric
2008-10-21 17:01 ` Mark Mitchell
2008-10-21 23:11 ` Richard Sandiford
2008-10-21 23:49 ` Mark Mitchell
2008-10-22 0:16 ` Thiemo Seufer
2008-10-22 1:05 ` Mark Mitchell
2008-10-22 6:36 ` Thiemo Seufer
2008-10-22 6:54 ` Mark Mitchell
2008-10-22 7:30 ` Weddington, Eric
2008-10-22 10:03 ` Richard Sandiford
2008-10-22 17:43 ` Mark Mitchell
2008-10-22 20:28 ` Richard Sandiford
2008-10-28 5:07 ` Fu, Chao-Ying
2008-10-29 8:05 ` Richard Sandiford
2008-10-16 22:34 ` Adam Nemet
2009-02-25 7:01 ` Fu, Chao-Ying
2009-02-25 9:35 ` Adam Nemet
2009-02-25 17:51 ` Daniel Jacobowitz
2009-02-26 9:48 ` Fu, Chao-Ying [this message]
2009-02-27 20:46 ` Maciej W. Rozycki
2009-02-28 10:15 ` Fu, Chao-Ying
2009-02-28 18:39 ` Maciej W. Rozycki
2008-10-17 11:40 Fu, Chao-Ying
2008-10-23 9:06 Ross Ridge
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='000e01c997b7$706b4f60$a914a8c0@mips.com' \
--to=fu@mips.com \
--cc=anemet@caviumnetworks.com \
--cc=davidlau@mips.com \
--cc=drow@false.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=mark@codesourcery.com \
--cc=rdsandiford@googlemail.com \
/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).