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: "cjohns at cybertec dot com dot au" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 3 Nov 2004 23:05:46 -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 cjohns at cybertec dot com dot au 2004-11-03 23:05 -------
Does this mean the instruction in question (cas) in atomicity.h cannot be used
on the 68060 if the stack can be aligned to a 2 byte boundary ?
Would a stack aligned this way cause a slow down if the call/ret address being
pushed and popped is not aligned to a 32bit boundary ?
I do not full understand the ABI issues hence my next question. RTEMS +
application is built as a single executable, typically all with the same tool
set, so does an ABI issue exist in our case ?
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=17627