public inbox for cgen@sourceware.org
 help / color / mirror / Atom feed
From: "龚 源泉" <source_kong@hotmail.com>
To: cgen@sources.redhat.com
Subject: problems about "building a GAS test suite"
Date: Tue, 27 Aug 2002 01:45:00 -0000	[thread overview]
Message-ID: <F2150pi8Zac4KPHMCIv000074b3@hotmail.com> (raw)

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=gb2312; format=flowed, Size: 2496 bytes --]

Dear Mr Ben,
     Sorry for bothering you again, but I think I've met a big problem. 
When I was building a 

GAS test suite following the CGEN manual(take m32r for example):

1.cd to the CGEN build directory 

2.make gas-test At this point two files have been created in the CGEN build 
directory: 

`gas-allinsn.exp' and `gas-build.sh'. The `gas-build.sh' script normally 
requires one command 

line argument: the location of your `gas' build directory. If this argument 
is omitted, the 

script searches in `../gas' automatically. 

3.Copy `gas-allinsn.exp' to 
`toplevel/gas/testsuite/gas/<arch>/allinsn.exp'. 

4.sh gas-build.sh At this point directory tmpdir contains two files: 
`allinsn.s' and 

`allinsn.d'. File `allinsn.d' usually needs a bit of massaging. 

5.Copy `tmpdir/allinsn.[sd]' to `toplevel/gas/testsuite/gas/<arch>' 

6.Run make check in the `gas' build directory and massage things until 
you're satisfied the 

files are correct. 

7.Check files into CVS.

I went through the first 3 steps successfully. In step 4, when I run "sh 
gas-build.sh (the 

directory where gas is build)", I got such error mssages:

allinsn.s: Assembler messages:
allinsn.s:8: Error: too many memory references for `add'
allinsn.s:12: Error: no such instruction: `add3 fp,fp,00'
allinsn.s:16: Error: too many memory references for `and'
allinsn.s:20: Error: no such instruction: `and3 fp,fp,0'
allinsn.s:24: Error: too many memory references for `or'
allinsn.s:28: Error: no such instruction: `or3 fp,fp,00'
allinsn.s:32: Error: too many memory references for `xor'
allinsn.s:36: Error: no such instruction: `xor3 fp,fp,0'
allinsn.s:40: Error: no such instruction: `addi fp,0'
allinsn.s:44: Error: no such instruction: `addv fp,fp'
allinsn.s:48: Error: no such instruction: `addv3 fp,fp,0'
...


I checked the file "gas-build.sh", it's head writes
#/bin/sh
# Generate test result data for m32r GAS testing.
# This script is machine generated.
# It is intended to be run in the testsuite source directory.

It sound's that the instructions given in this file should be m32r's 
instructions, but why the 

above message shows "no such instruction", where on earth does the 
contradiction lie?


I'm very anxious to know the answer, thank you! 
 
                                                                  
yours:Jacky


_________________________________________________________________
ÏíÓÃÊÀ½çÉÏ×î´óµÄµç×ÓÓʼþϵͳ¡ª MSN Hotmail¡£http://www.hotmail.com/cn

             reply	other threads:[~2002-08-27  8:45 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-27  1:45 龚 源泉 [this message]
2002-08-27  3:46 ` Frank Ch. Eigler
     [not found] <002c01c24dd0$2ef01ee0$7f6f0e0a@gongyq>
2002-08-27  7:17 ` Frank Ch. Eigler

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=F2150pi8Zac4KPHMCIv000074b3@hotmail.com \
    --to=source_kong@hotmail.com \
    --cc=cgen@sources.redhat.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).