public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Gary Thomas <gary@mlbassoc.com>
To: James Yates <j.yates@quartzuk.com>
Cc: ecos-discuss@sources.redhat.com
Subject: RE: [ECOS] Problems with var_mk_defs.c
Date: Wed, 15 Oct 2003 15:50:00 -0000	[thread overview]
Message-ID: <1066233034.32461.57.camel@hermes> (raw)
In-Reply-To: <CB39E7B8FC98924D85DFBED207E4CC9834420D@ip02.quartzelec.adsl.gxn.net>

On Wed, 2003-10-15 at 09:46, James Yates wrote:
> After looking at the generated var_mk_defs.s file by adding -save-temps to the global compiler flags, the first line the compiler complains about is:
> 
> .equ	HAL_UCACHE_SIZE, #0
> .loc 1 82 0
> 
> Would I be right in assuming that this should read:
> 
> .equ	HAL_UCACHE_SIZE, 0
> .loc 1 82 0
> 
> The function call that creates this line is:
> DEFINE(HAL_UCACHE_SIZE, HAL_UCACHE_SIZE);
> 
> The macro itself:
> #define DEFINE(sym, val) \
>         asm volatile("\n\t.equ\t" #sym ", %0" : : "i" (val))
> 
> I guess this is the assembler equivalent of #define HAL_UCACHE_SIZE 0 so that wherever HAL_UCACHE_SIZE is referenced, the value of 0 is used.
> 
> However, I am unsure about how to modify the macro, my skill in assembler is extremely poor. Any ideas?
> 

It looks right to me.  It seems that different assemblers (and
even different versions sometimes) want to see this written
differently.

Give it a try (sans "#") and see what happens.

-- 
Gary Thomas <gary@mlbassoc.com>
MLB Associates


-- 
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss

  reply	other threads:[~2003-10-15 15:50 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-15 15:45 James Yates
2003-10-15 15:50 ` Gary Thomas [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-10-16  7:55 James Yates
2003-10-16 12:04 ` Gary Thomas
2003-10-15 15:02 James Yates
2003-10-15 15:09 ` Gary Thomas
2003-10-15 14:34 James Yates
2003-10-15 14:41 ` Gary Thomas

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=1066233034.32461.57.camel@hermes \
    --to=gary@mlbassoc.com \
    --cc=ecos-discuss@sources.redhat.com \
    --cc=j.yates@quartzuk.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).