From: "Joerg Rapka" <joerg.rapka@duagon.com>
To: <ecos-discuss@sourceware.cygnus.com>
Subject: [ECOS] assertion checks for stack
Date: Wed, 10 Jan 2001 05:15:00 -0000 [thread overview]
Message-ID: <NDBBKEBGMLIMMPMJHHFDMECGCLAA.joerg.rapka@duagon.com> (raw)
In-Reply-To: <wwgn1czejz6.fsf@balti.cambridge.redhat.com>
Hello all
I have some trouble with assertion checks for the stack
in file "packages/kernel/current/include/thread.inl".
The assertion checks uses the type "CYG_WORD" for alignment tests.
This type "CYG_WORD" is defined in file
"packages/infra/current/include/cyg_type.h".
It is of type "cyg_uint32" (that's fixed - so it should have always 32
bits).
So the assertion checks for the stack requires a 32-bit alignment of the
stack address.
I'm using the following:
- Motorola M68331 CPU
- latest CVS sources
- template "elix" (without network support)
On my target the assertion check generates a failure, if it checks the main
stack.
This main stack is defined in file
"packages/compat/posix/current/src/pthread.cxx"
in the following way:
static char main_stack[CYGNUM_LIBC_MAIN_DEFAULT_STACK_SIZE];
This error happens, since the m68k GNU compiler will align the "main_stack"
to 16-bit alignment.
How should I solve the problem?
I cannot (will not) modify the definition of the "main_stack" in file
"pthread.cxx"
either I cannot modify the type definition of "CYG_WORD" in file
"cyg_type.h" (since
this type must have 32-bit - as I understood the rest of the source code).
Thanks in advance for any help or tips.
Best regards, Joerg
next prev parent reply other threads:[~2001-01-10 5:15 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-09 14:59 [ECOS] Regarding to eCos on VRC4373 Ling Su
2001-01-09 16:44 ` Jonathan Larmour
2001-01-09 23:37 ` Ling Su
2001-01-10 3:30 ` Nick Garnett
2001-01-10 5:15 ` Joerg Rapka [this message]
2001-01-10 9:10 ` Jonathan Larmour
2001-01-10 0:19 ` Ling Su
2001-01-10 9:08 ` Jonathan Larmour
[not found] ` <005e01c07ad5$5ba58210$0301a8c0@leopard>
2001-01-10 9:17 ` Jonathan Larmour
2001-01-10 14:08 ` Ling Su
2001-01-10 14:17 ` Jonathan Larmour
2001-01-10 15:45 ` Grant Edwards
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=NDBBKEBGMLIMMPMJHHFDMECGCLAA.joerg.rapka@duagon.com \
--to=joerg.rapka@duagon.com \
--cc=ecos-discuss@sourceware.cygnus.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).