From: "'Rask Ingemann Lambertsen'" <rask@sygehus.dk>
To: Pompapathi V Gadad <Pompapathi.V.Gadad@nsc.com>
Cc: Pompapathi V Gadad <pompapathi@gmail.com>, gcc-patches@gcc.gnu.org
Subject: Re: [Patch] New: CR16 port
Date: Mon, 16 Jul 2007 12:25:00 -0000 [thread overview]
Message-ID: <20070716115108.GG5690@sygehus.dk> (raw)
In-Reply-To: <469B32A6.6090009@nsc.com>
On Mon, Jul 16, 2007 at 02:26:06PM +0530, Pompapathi V Gadad wrote:
> Index: doc/extend.texi
> ===================================================================
> --- doc/extend.texi (revision 126669)
> +++ doc/extend.texi (working copy)
> @@ -2100,11 +2100,10 @@ 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
> SH processors can be specified via the @code{interrupt_handler} attribute.
You're still modifying the m68k documentation.
> Index: config/cr16/cr16.md
[...]
> +(define_mode_attr tIsa [(QI "b") (HI "w") (SI "d") (SF "d")])
> +(define_mode_attr tIsaLong [ (SI "d") (SF "d")])
> +(define_mode_attr tIsaShort [(QI "b") (HI "w") ])
You should be able to use tIsa instead of tIsaLong and tIsaShort
everywhere.
> +(define_mode_attr lImmShort [(QI "4") (HI "4") ])
> +(define_mode_attr lImmLong [ (SI "6") (SF "6")])
> +(define_mode_attr lImmArith [(QI "4") (HI "4") (SI "6") (SF "6")])
And something similiar goes here.
> +;; Negation Instructions
> +; move 0,r sub x,r. More efficient than xor -1,x add 1,x
> +(define_expand "neg<mode>2"
> + [(set (match_operand:CR16IM 0 "register_operand" "")
> + (const_int 0))
> + (parallel [(set (match_dup 0)
> + (minus:CR16IM (match_dup 0)
> + (match_operand:CR16IM 1 "register_operand" "")))
> + (clobber (reg:CC CC_REGNUM))])
> + ]
> + ""
> + "")
You said you would delete this expander. Did it not work?
--
Rask Ingemann Lambertsen
next prev parent reply other threads:[~2007-07-16 11:51 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' [this message]
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
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=20070716115108.GG5690@sygehus.dk \
--to=rask@sygehus.dk \
--cc=Pompapathi.V.Gadad@nsc.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=pompapathi@gmail.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).