From: Rask Ingemann Lambertsen <rask@sygehus.dk>
To: "Gadad, Pompapathi V" <Pompapathi.V.Gadad@nsc.com>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: [Patch] New: CR16 port
Date: Fri, 13 Jul 2007 15:56:00 -0000 [thread overview]
Message-ID: <20070713144841.GC5690@sygehus.dk> (raw)
In-Reply-To: <174557.128221184049955220.JavaMail.root@postal04.nsc.com>
On Tue, Jul 10, 2007 at 06:45:55AM +0000, Gadad, Pompapathi V wrote:
> Index: doc/extend.texi
> ===================================================================
> --- doc/extend.texi (revision 126478)
> +++ doc/extend.texi (working copy)
> @@ -2078,13 +2078,12 @@ This attribute is ignored for R8C target
>
> @item interrupt
> @cindex interrupt handler functions
> -Use this attribute on the ARM, AVR, C4x, CRX, M32C, M32R/D, m68k, MS1,
> -and Xstormy16 ports to indicate that the specified function is an
> -interrupt handler. The compiler will generate function entry and exit
> -sequences suitable for use in an interrupt handler when this attribute
> -is present.
> +Use this attribute on the ARM, AVR, C4x, CR16, CRX, M32C, M32R/D, MS1,
> +and Xstormy16 ports to indicate that the specified function is an interrupt
> +handler. The compiler will generate function entry and exit sequences suitable
> +for use in an interrupt handler when this attribute is present.
>
> -Note, interrupt handlers for the Blackfin, H8/300, H8/300H, H8S, and
> +Note, interrupt handlers for the Blackfin, m68k, H8/300, H8/300H, H8S, and
> SH processors can be specified via the @code{interrupt_handler} attribute.
>
> Note, on the AVR, interrupts will be enabled inside the function.
This part of your patch changes the m68k documentation, which I guess it
shouldn't.
--
Rask Ingemann Lambertsen
prev parent reply other threads:[~2007-07-13 14:48 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-10 7:11 Gadad, Pompapathi V
2007-07-11 23:41 ` Rask Ingemann Lambertsen
2007-07-13 9:22 ` Pompapathi V Gadad
2007-07-13 15:23 ` Rask Ingemann Lambertsen
2007-07-14 4:00 ` Pompapathi V Gadad
2007-07-16 9:14 ` Pompapathi V Gadad
2007-07-16 12:25 ` 'Rask Ingemann Lambertsen'
2007-07-16 13:01 ` Pompapathi V Gadad
2007-07-16 13:08 ` Pompapathi V Gadad
2007-07-20 9:48 ` Pompapathi V Gadad
2007-07-21 14:33 ` 'Rask Ingemann Lambertsen'
2007-07-25 9:40 ` Pompapathi V Gadad
2007-07-30 8:33 ` 'Rask Ingemann Lambertsen'
2007-07-30 9:14 ` Pompapathi V Gadad
2007-08-03 13:03 ` 'Rask Ingemann Lambertsen'
2007-08-06 4:44 ` Pompapathi V Gadad
2007-08-06 10:43 ` 'Rask Ingemann Lambertsen'
2007-08-06 10:49 ` Pompapathi V Gadad
2007-07-21 12:20 ` 'Rask Ingemann Lambertsen'
2007-07-13 15:56 ` Rask Ingemann Lambertsen [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=20070713144841.GC5690@sygehus.dk \
--to=rask@sygehus.dk \
--cc=Pompapathi.V.Gadad@nsc.com \
--cc=gcc-patches@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).