[Bug libstdc++/17627] M68060 fails with libstdc++-v3/config/cpu/m68k/atomicity.h

2005-08-16 Thread pinskia at gcc dot gnu dot org
--- Additional Comments From pinskia at gcc dot gnu dot org 2005-08-17 03:13 --- No feedback in more than 6 months. -- What|Removed |Added Status|WAITING

[Bug libstdc++/17627] M68060 fails with libstdc++-v3/config/cpu/m68k/atomicity.h

2005-02-06 Thread cjohns at cybertec dot com dot au
--- Additional Comments From cjohns at cybertec dot com dot au 2005-02-07 05:06 --- No change. I have arranged to get the MVME172 card back for an afternoon later this week (11-Feb-2005). I will have a look then. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=17627

[Bug libstdc++/17627] M68060 fails with libstdc++-v3/config/cpu/m68k/atomicity.h

2005-02-06 Thread pinskia at gcc dot gnu dot org
--- Additional Comments From pinskia at gcc dot gnu dot org 2005-02-07 04:51 --- Any news on this? -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=17627

[Bug libstdc++/17627] M68060 fails with libstdc++-v3/config/cpu/m68k/atomicity.h

2004-11-04 Thread joel at oarcorp dot com
--- Additional Comments From joel at oarcorp dot com 2004-11-04 19:11 --- Subject: Re: M68060 fails with libstdc++-v3/config/cpu/m68k/atomicity.h schwab at suse dot de wrote: > --- Additional Comments From schwab at suse dot de 2004-11-04 16:53 --- > You can't just increase the

[Bug libstdc++/17627] M68060 fails with libstdc++-v3/config/cpu/m68k/atomicity.h

2004-11-04 Thread schwab at suse dot de
--- Additional Comments From schwab at suse dot de 2004-11-04 16:53 --- You can't just increase the alignment as that would break the ABI. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=17627

[Bug libstdc++/17627] M68060 fails with libstdc++-v3/config/cpu/m68k/atomicity.h

2004-11-04 Thread joel at oarcorp dot com
--- Additional Comments From joel at oarcorp dot com 2004-11-04 16:37 --- Subject: Re: M68060 fails with libstdc++-v3/config/cpu/m68k/atomicity.h schwab at suse dot de wrote: > --- Additional Comments From schwab at suse dot de 2004-11-04 15:12 --- > My copy of the 68060 user m

[Bug libstdc++/17627] M68060 fails with libstdc++-v3/config/cpu/m68k/atomicity.h

2004-11-04 Thread schwab at suse dot de
--- Additional Comments From schwab at suse dot de 2004-11-04 15:12 --- My copy of the 68060 user manual says that the MC68060ISP does contain an emulation for unaligned CAS. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=17627

[Bug libstdc++/17627] M68060 fails with libstdc++-v3/config/cpu/m68k/atomicity.h

2004-11-04 Thread joel at oarcorp dot com
--- Additional Comments From joel at oarcorp dot com 2004-11-04 14:56 --- Subject: Re: M68060 fails with libstdc++-v3/config/cpu/m68k/atomicity.h schwab at suse dot de wrote: > --- Additional Comments From schwab at suse dot de 2004-11-03 23:44 --- > Even the 68020 should alrea

[Bug libstdc++/17627] M68060 fails with libstdc++-v3/config/cpu/m68k/atomicity.h

2004-11-03 Thread peter at the-baradas dot com
--- Additional Comments From peter at the-baradas dot com 2004-11-04 02:17 --- Chris Johns <[EMAIL PROTECTED]> asked me: >Is the Coldfire aligned to a 2 byte boundary or a 4 byte boundary ? The Colfire operates the same as the x86 in that the cache/bus unit will automagically handle una

[Bug libstdc++/17627] M68060 fails with libstdc++-v3/config/cpu/m68k/atomicity.h

2004-11-03 Thread schwab at suse dot de
--- Additional Comments From schwab at suse dot de 2004-11-03 23:44 --- Even the 68020 should already show slight improvement when using 4 byte aligment due to the 32 bit data bus (the 68000/010 only have a 16 bit data bus). Adding an aligned attribute to the _Atomic_int type doesn't

[Bug libstdc++/17627] M68060 fails with libstdc++-v3/config/cpu/m68k/atomicity.h

2004-11-03 Thread joel at oarcorp dot com
--- Additional Comments From joel at oarcorp dot com 2004-11-03 23:25 --- 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-11-03 23:05 > --- >

[Bug libstdc++/17627] M68060 fails with libstdc++-v3/config/cpu/m68k/atomicity.h

2004-11-03 Thread cjohns at cybertec dot com dot au
--- 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

[Bug libstdc++/17627] M68060 fails with libstdc++-v3/config/cpu/m68k/atomicity.h

2004-11-03 Thread joel at oarcorp dot com
--- Additional Comments From joel at oarcorp dot com 2004-11-03 22:56 --- Subject: Re: M68060 fails with libstdc++-v3/config/cpu/m68k/atomicity.h schwab at suse dot de wrote: > --- Additional Comments From schwab at suse dot de 2004-11-03 22:25 --- > On the m68k the biggest ali

[Bug libstdc++/17627] M68060 fails with libstdc++-v3/config/cpu/m68k/atomicity.h

2004-11-03 Thread schwab at suse dot de
--- Additional Comments From schwab at suse dot de 2004-11-03 22:25 --- On the m68k the biggest alignment has traditionally only been 2 bytes (inherited from the Sun compiler, AFAIK), and it's only overridden on NetBSD (and previously on some configurations that are removed now) or when

[Bug libstdc++/17627] M68060 fails with libstdc++-v3/config/cpu/m68k/atomicity.h

2004-11-03 Thread joel at oarcorp dot com
--- Additional Comments From joel at oarcorp dot com 2004-11-03 21:09 --- Subject: Re: M68060 fails with libstdc++-v3/config/cpu/m68k/atomicity.h bkoz at gcc dot gnu dot org wrote: > --- Additional Comments From bkoz at gcc dot gnu dot org 2004-11-03 00:12 > --- > > Joel, you

[Bug libstdc++/17627] M68060 fails with libstdc++-v3/config/cpu/m68k/atomicity.h

2004-11-02 Thread bkoz at gcc dot gnu dot org
--- Additional Comments From bkoz at gcc dot gnu dot org 2004-11-03 00:12 --- Joel, you might want to talk to the m68k maintainers. Take your pick: m68hc11 portStephane Carrez [EMAIL PROTECTED] m68k port (?) Jeff Law[EMAIL PROTECTED] m68k-m

[Bug libstdc++/17627] M68060 fails with libstdc++-v3/config/cpu/m68k/atomicity.h

2004-11-02 Thread cvs-commit at gcc dot gnu dot org
--- Additional Comments From cvs-commit at gcc dot gnu dot org 2004-11-02 23:57 --- Subject: Bug 17627 CVSROOT:/cvs/gcc Module name:gcc Changes by: [EMAIL PROTECTED] 2004-11-02 23:56:57 Modified files: libstdc++-v3 : ChangeLog libstdc++-v3/src:

[Bug libstdc++/17627] M68060 fails with libstdc++-v3/config/cpu/m68k/atomicity.h

2004-11-02 Thread joel at gcc dot gnu dot org
--- Additional Comments From joel at gcc dot gnu dot org 2004-11-02 12:28 --- I emailed Chris privately. The stack is properly aligned. But his target is not setup at the moment and he would have to build a special toolset without his workwound/fix in place. He won't be able to do this

[Bug libstdc++/17627] M68060 fails with libstdc++-v3/config/cpu/m68k/atomicity.h

2004-11-01 Thread bkoz at gcc dot gnu dot org
--- Additional Comments From bkoz at gcc dot gnu dot org 2004-11-01 20:02 --- Will close unless update. -benjamin -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=17627