From mint-bounce@lists.fishpool.fi Sun Jun 13 06:47:38 2010 Message-ID: <4C14B6C8.3020400@freesbee.fr> Date: Sun, 13 Jun 2010 12:45:28 +0200 From: =?ISO-8859-1?Q?Vincent_Rivi=E8re?= User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; fr; rv:1.9.1.9) Gecko/20100317 Thunderbird/3.0.4 MIME-Version: 1.0 To: mint@lists.fishpool.fi Subject: Re: [MiNT] MiNTLib 0.59.1 for your testing pleasure.... References: <4C0FC5E4.5040306@freesbee.fr> <4C0FD5A0.7030809@atari-source.org> <4C147D55.7080404@freesbee.fr> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed X-ecartis-version: Ecartis v1.0.0 Sender: mint-bounce@lists.fishpool.fi Errors-to: mint-bounce@lists.fishpool.fi X-original-sender: vincent.riviere@freesbee.fr Precedence: bulk List-help: List-unsubscribe: List-Id: X-List-ID: List-subscribe: List-owner: List-post: Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by mail.sparemint.org id o5DAlbQG019897 Paul Wratt wrote: > If 2.95.3 sources were to be updated to be compiled with 4.x.x, (if I > were doing it) I would at least have a look at the current patches to > see what was involved with adding CF support. Or am I missing, or over > simplifying, something here.. In the official GCC sources, support for some ColdFire CPUs has appeared in GCC 3.x or something like this. The ColdFire V4e is supported since GCC 4.x. GCC 2.x is unable to produce code for ColdFire. It is a lot of work to add support for a new target CPU in GCC. Feel free to do it yourself, if you like. -- Vincent Rivière