From: "James Yates" <j.yates@quartzuk.com>
To: <ecos-discuss@sources.redhat.com>
Subject: [ECOS] Problems with var_mk_defs.c
Date: Wed, 15 Oct 2003 14:34:00 -0000 [thread overview]
Message-ID: <CB39E7B8FC98924D85DFBED207E4CC9831F8F8@ip02.quartzelec.adsl.gxn.net> (raw)
In the SH Hal architecture I am getting build problems relating to var_mk_defs.c. If I comment out the code within int main(void), the compile problems go away. When included, every call to DEFINE throws up a bad expression. Can anyone explain to me what this file is actually doing, or indeed why it isn't working as I am completely stuck.
#define DEFINE(sym, val) \
asm volatile("\n\t.equ\t" #sym ",%0" : : "i" (val))
int main(void)
{
// Caching details
DEFINE(HAL_UCACHE_SIZE, HAL_UCACHE_SIZE);
DEFINE(HAL_UCACHE_WAYS, HAL_UCACHE_WAYS);
DEFINE(HAL_UCACHE_LINE_SIZE, HAL_UCACHE_LINE_SIZE);
// Interrupt details
DEFINE(CYGNUM_HAL_ISR_MAX, CYGNUM_HAL_ISR_MAX);
DEFINE(CYGNUM_HAL_INTERRUPT_LVL0, CYGNUM_HAL_INTERRUPT_LVL0);
DEFINE(CYGNUM_HAL_INTERRUPT_LVL_MAX, CYGNUM_HAL_INTERRUPT_LVL_MAX);
#ifdef CYGNUM_HAL_INTERRUPT_LVL14
DEFINE(CYGNUM_HAL_INTERRUPT_LVL14, CYGNUM_HAL_INTERRUPT_LVL14);
#endif
DEFINE(CYGNUM_HAL_INTERRUPT_NMI, CYGNUM_HAL_INTERRUPT_NMI);
DEFINE(CYGNUM_HAL_VECTOR_TRAP, CYGNUM_HAL_VECTOR_TRAP);
DEFINE(CYGNUM_HAL_VECTOR_INTERRUPT, CYGNUM_HAL_VECTOR_INTERRUPT);
return 0;
}
Many Thanks in advance
James Yates
--
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss
next reply other threads:[~2003-10-15 14:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-15 14:34 James Yates [this message]
2003-10-15 14:41 ` Gary Thomas
2003-10-15 15:02 James Yates
2003-10-15 15:09 ` Gary Thomas
2003-10-15 15:45 James Yates
2003-10-15 15:50 ` Gary Thomas
2003-10-16 7:55 James Yates
2003-10-16 12:04 ` 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=CB39E7B8FC98924D85DFBED207E4CC9831F8F8@ip02.quartzelec.adsl.gxn.net \
--to=j.yates@quartzuk.com \
--cc=ecos-discuss@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).