From: Doug Evans <dje@sebabeach.org>
To: Alan Modra <amodra@bigpond.net.au>
Cc: cgen@sourceware.org
Subject: Re: m32r cgen errors
Date: Fri, 25 Sep 2009 15:27:00 -0000 [thread overview]
Message-ID: <4ABCE160.6060607@sebabeach.org> (raw)
In-Reply-To: <20090925020923.GF18973@bubble.grove.modra.org>
Alan Modra wrote:
> Fixes the following error. OK to apply?
>
> cgen -s /src/binutils-current/opcodes/../cgen/cgen-opc.scm -s /src/binutils-current/opcodes/../cgen -v -f opinst -m all -a /src/binutils-current/opcodes/../cpu/m32r.cpu -OPC /src/binutils-current/opcodes/../cpu/m32r.opc -H tmp-26602-desc.h1 -C tmp-26602-desc.c1 -O tmp-26602-opc.h1 -P tmp-26602-opc.c1 -L tmp-26602-ibld.in1 -A tmp-26602-asm.in1 -D tmp-26602-dis.in1 -Q tmp-26602-opinst.c1
> Setting option `opinst' to "".
> Loading cpu description /src/binutils-current/opcodes/../cpu/m32r.cpu ...
> machs: all
> isas: all
> options: opinst
> trace:
> diags:
> Including file /src/binutils-current/opcodes/../cpu/simplify.inc ...
> ERROR: In procedure list:
> ERROR: end of file in /src/binutils-current/opcodes/../cpu/m32r.cpu
> make[5]: *** [run-cgen] Error 1
>
> * m32r.cpu (stb-plus): Typo fix.
>
> Index: cpu/m32r.cpu
> ===================================================================
> RCS file: /cvs/src/src/cpu/m32r.cpu,v
> retrieving revision 1.6
> diff -u -p -r1.6 m32r.cpu
> --- cpu/m32r.cpu 23 Sep 2009 22:30:55 -0000 1.6
> +++ cpu/m32r.cpu 25 Sep 2009 02:06:11 -0000
> @@ -2108,7 +2108,7 @@
> (sequence ((WI new-src2))
> (set new-src2 src2)
> (set (mem QI new-src2) src1)
> - (set src2 (add new-src2 (const 1)))
> + (set src2 (add new-src2 (const 1))))
> ((m32rx (unit u-store)
> (unit u-exec (in dr src2) (out dr src2) (cycles 0)))
> (m32r2 (unit u-store)
>
>
Thanks! And sorry!
[given all the testing I did, I don't know how this got missed, blech]
prev parent reply other threads:[~2009-09-25 15:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-25 2:09 Alan Modra
2009-09-25 15:27 ` Doug Evans [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=4ABCE160.6060607@sebabeach.org \
--to=dje@sebabeach.org \
--cc=amodra@bigpond.net.au \
--cc=cgen@sourceware.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).