This is the mail archive of the gcc-help@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: Forcing use of move instead of movem on M68k (5200/5307)

From: Ian Lance Taylor <iant at google dot com>
To: Richard Baverstock <rbaverst at engmail dot uwaterloo dot ca>
Cc: gcc-help at gcc dot gnu dot org
Date: 23 Mar 2007 16:00:37 -0700
Subject: Re: Forcing use of move instead of movem on M68k (5200/5307)
References: <9D2873BB-D515-48E4-8DE5-69C17EB89470@engmail.uwaterloo.ca> <m3ircsaqcd.fsf@localhost.localdomain> <5333517B-B1DB-4C16-8831-19B245B26426@engmail.uwaterloo.ca>

Richard Baverstock <rbaverst@engmail.uwaterloo.ca> writes:

> We're using 2.95.3 and 3.4.6 (tried both versions), so nothing really
> recent.
> 
> Trying the most recent one (4.1.2) would be a better idea? Or would a
> more recent version of the 3.x series be better?

Certainly the support for ColdFire has improved in 4.1.2.  I don't
know whether this specific problem has been fixed.

Ian

References:
- Forcing use of move instead of movem on M68k (5200/5307)
  - From: Richard Baverstock
- Re: Forcing use of move instead of movem on M68k (5200/5307)
  - From: Ian Lance Taylor
- Re: Forcing use of move instead of movem on M68k (5200/5307)
  - From: Richard Baverstock

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]