This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug libstdc++/17627] M68060 fails with libstdc++-v3/config/cpu/m68k/atomicity.h
- From: "joel at oarcorp dot com" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 23 Sep 2004 11:14:58 -0000
- Subject: [Bug libstdc++/17627] M68060 fails with libstdc++-v3/config/cpu/m68k/atomicity.h
- References: <20040923035910.17627.cjohns@cybertec.com.au>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Additional Comments From joel at oarcorp dot com 2004-09-23 11:14 -------
Subject: Re: M68060 fails with libstdc++-v3/config/cpu/m68k/atomicity.h
cjohns at cybertec dot com dot au wrote:
> ------- Additional Comments From cjohns at cybertec dot com dot au 2004-09-23 10:20 -------
> Agreed. The section C.2.2.3 of the user manual states this is the case when it
> details the emulation software.
>
> So is the alignment issue in the stack based __result and (if yes) then __temp ?
>
> If this is true could this be an RTEMS stack initialisation issue ? That is, I
> would expect GCC to keep the stack aligned for the 68060.
Each RTEMS task stack is supposed to start out at least 4 byte aligned.
The heap only returns things that way. :)
Chris could you check the starting stack pointer in the TCB and the
current SP just before this code?
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=17627