public inbox for cgen@sourceware.org
 help / color / mirror / Atom feed
From: Shehryar Humayun <shehryarhumayunkhan@yahoo.com>
To: Doug Evans <dje@transmeta.com>
Cc: cgen@sources.redhat.com
Subject: Re: Problem in opcodes for ARM
Date: Fri, 06 Sep 2002 11:37:00 -0000	[thread overview]
Message-ID: <20020906174719.76052.qmail@web21202.mail.yahoo.com> (raw)
In-Reply-To: <15736.53665.870769.75252@casey.transmeta.com>

Hi,
Here is the complete output I get when I run
       make opcodes ARCH=arm 
in my build directory, after configuring it for arm
+++++++++++++++++++++++++++++++++++++++++++++++++++++
>make opcodes ARCH=arm
rm -f tmp-opc.h tmp-itab.c
	rm -f tmp-asm.in tmp-dis.in tmp-ibld.h tmp-ibld.in
`if test -f ../guile/libguile/guile ; then echo
../guile/libguile/guile; else echo guile ; fi' -s
/root/src/cgen-1.0/cgen/cgen-opc.scm \ 
	-s /root/src/cgen-1.0/cgen \
	-v \
	-f " opinst" \
	-m all -a arm \
	-O tmp-opc.h -P tmp-opc.c -Q tmp-opinst.c \
	-B tmp-ibld.h -L tmp-ibld.in \
	-A tmp-asm.in -D tmp-dis.in
Skipping slib/sort, already loaded.
Skipping slib/random, already loaded.
cgen -s /root/src/cgen-1.0/cgen/cgen-opc.scm -s
/root/src/cgen-1.0/cgen -v -f " opinst" -m all -a arm
-O tmp-opc.h -P tmp-opc.c -Q tmp-opinst.c -B
tmp-ibld.h -L tmp-ibld.in -A tmp-asm.in -D tmp-dis.in
Setting option 'opinst' to "".
Loading cpu discription
/root/src/cgen-1.0/cgen/cpu/arm.cpu
Including simplify.inc
Including arm7.cpu
Including thumb.cpu
Analyzing Instruction Set
Done Analysis
Generating arm-opc.h
Generating arm-opc.c
Generating arm-opcinst.c
Generating arm-ibld.h
Generating arm-ibld.in
ERROR: missing operands: "(sra () WI (sub WI
value 2))"
No backtrace available
make: *** [opcodes] Error 1
+++++++++++++++++++++++++++++++++++++++++++++++++++++++

BTW, (sra () WI (sub WI value 2)) exists on line 87 in
arm7.cpu file in the cgen/cpu directory. 

--- Doug Evans <dje@transmeta.com> wrote:
> fwiw. don't edit your sessions and only send what
> appears to be
> the highlights.  Send the _entire_ session. 
>Seriously.

I just try to keep the mail size to the minimum. 

Regards

Shehryar

__________________________________________________
Do You Yahoo!?
Yahoo! Finance - Get real-time stock quotes
http://finance.yahoo.com

  reply	other threads:[~2002-09-06 18:37 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-01  2:03 Next Step Shehryar Humayun
2002-09-03  7:23 ` Ben Elliston
2002-09-03 20:51   ` Shehryar Humayun
2002-09-04 11:11     ` Ben Elliston
2002-09-04 19:42       ` Shehryar Humayun
2002-09-05  2:30         ` Ben Elliston
2002-09-05 16:22           ` Shehryar Humayun
2002-09-06  6:55             ` Ben Elliston
2002-09-06  7:37               ` Problem in opcodes for ARM Shehryar Humayun
2002-09-06  9:02                 ` Doug Evans
2002-09-06 11:37                   ` Shehryar Humayun [this message]
2002-09-06  9:36               ` Next Step Shehryar Humayun
2002-09-06 10:03                 ` Ben Elliston
2002-09-06 11:21                   ` Shehryar Humayun
2002-09-06 12:07                     ` Ben Elliston
2002-09-06 20:54                       ` Shehryar Humayun
2002-09-09  6:27                         ` Ben Elliston
2002-09-03 20:51   ` Shehryar Humayun

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=20020906174719.76052.qmail@web21202.mail.yahoo.com \
    --to=shehryarhumayunkhan@yahoo.com \
    --cc=cgen@sources.redhat.com \
    --cc=dje@transmeta.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).