Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: "Kevin D. Kissell" <kevink@mips.com>
To: "John Miller" <jamiller1110@cox.net>, <linux-mips@linux-mips.org>
Subject: Re: Instruction error with cache opcode
Date: Sun, 14 May 2006 21:42:46 +0200	[thread overview]
Message-ID: <009501c6778e$947c3ff0$10eca8c0@grendel> (raw)
In-Reply-To: 4467796E.8060000@mountolympos.net

> > Where and how is the value of Index_Store_Tag_I  defined?
> 
> I included asm/cacheops.h from the kernel tree, it is defined there as :
> 
> #define Index_Store_Tag_I 0x08
> 
> I also tried to substitute 0x08 directly into my source and I got the
> same error.  Strangely enough, if I remove the include line, I get the
> same exact error.

Have you got your sources properly installes so that include/asm is
a symlink to include/asm-mips?  I've done the experiment at my end,
and it builds just fine so long as regdef.h and cacheops.h are really
on the include path of the compilation.  If they're not, I get:

[kevink@cthulhu tmp]$ mipsel-linux-gcc -I ~/smtchead/include -c cacheop.S
cacheop.S: Assembler messages:
cacheop.S:4: Error: Instruction cache requires absolute expression
cacheop.S:4: Error: Instruction cache requires absolute expression
cacheop.S:4: Error: illegal operands `cache'

            Regards,

            Kevin K.

WARNING: multiple messages have this Message-ID (diff)
From: "Kevin D. Kissell" <kevink@mips.com>
To: John Miller <jamiller1110@cox.net>, linux-mips@linux-mips.org
Subject: Re: Instruction error with cache opcode
Date: Sun, 14 May 2006 21:42:46 +0200	[thread overview]
Message-ID: <009501c6778e$947c3ff0$10eca8c0@grendel> (raw)
Message-ID: <20060514194246.p6XhRZPyIPLe3q6VKt89kqur5r4ZtvShmYRD5xIqNig@z> (raw)
In-Reply-To: 4467796E.8060000@mountolympos.net

> > Where and how is the value of Index_Store_Tag_I  defined?
> 
> I included asm/cacheops.h from the kernel tree, it is defined there as :
> 
> #define Index_Store_Tag_I 0x08
> 
> I also tried to substitute 0x08 directly into my source and I got the
> same error.  Strangely enough, if I remove the include line, I get the
> same exact error.

Have you got your sources properly installes so that include/asm is
a symlink to include/asm-mips?  I've done the experiment at my end,
and it builds just fine so long as regdef.h and cacheops.h are really
on the include path of the compilation.  If they're not, I get:

[kevink@cthulhu tmp]$ mipsel-linux-gcc -I ~/smtchead/include -c cacheop.S
cacheop.S: Assembler messages:
cacheop.S:4: Error: Instruction cache requires absolute expression
cacheop.S:4: Error: Instruction cache requires absolute expression
cacheop.S:4: Error: illegal operands `cache'

            Regards,

            Kevin K.

  reply	other threads:[~2006-05-14 19:39 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-14 13:51 Instruction error with cache opcode John Miller
2006-05-14 13:51 ` John Miller
2006-05-14 14:17 ` Kevin D. Kissell
2006-05-14 14:17   ` Kevin D. Kissell
2006-05-14 18:39   ` John Miller
2006-05-14 19:42     ` Kevin D. Kissell [this message]
2006-05-14 19:42       ` Kevin D. Kissell
2006-05-14 20:14       ` John Miller
2006-05-14 23:29         ` Thiemo Seufer
2006-05-15  1:06     ` Atsushi Nemoto
2006-05-15  1:35       ` John Miller
2006-05-15  1:38         ` John Miller
2006-05-15  1:38           ` John Miller

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='009501c6778e$947c3ff0$10eca8c0@grendel' \
    --to=kevink@mips.com \
    --cc=jamiller1110@cox.net \
    --cc=linux-mips@linux-mips.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