From mint-bounce@lists.fishpool.fi Tue Jan 19 11:05:01 2010 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:sender:message-id:date:from :user-agent:mime-version:to:subject:references:in-reply-to :content-type:content-transfer-encoding; bh=gaPRXArQepMIaB4LHO4hxlOsuqYyKAH7LKg9vAISJ44=; b=U+LCbdVjkiFgH0RViIgF9qoPdkwXXLjtqE/FvThHhfsEo4ZCMcZzPlgEPIbiqm/2hk cXg2917J7HrTvkz+VCKqK2mRnkrIHB3LSaMmAjS/ZASBo0cNpvhUFzAiXI6DLBuz1AO3 NAPgpllrn/mFjfh/Y+LLVsxH4qgcv1NIPnC5s= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:message-id:date:from:user-agent:mime-version:to:subject :references:in-reply-to:content-type:content-transfer-encoding; b=Ep23+TqbBACNeCsfwqG2aCiLLQW/sF9HgZPDkNYqdmSU/1HKwGSklGloVlYRBZ46H7 zMHhUpr5InV4RLJ9mPl93TQvkyrTCecCMOX255cNsoY0jWQqnVZq8kGxYHpDoL5R0mSX ZGJy2toxUmXF+L0cngID2xXpqoAK+MY7sf9qU= Message-ID: <4B55D604.60805@freesbee.fr> Date: Tue, 19 Jan 2010 16:55:48 +0100 From: =?UTF-8?B?VmluY2VudCBSaXZpw6hyZQ==?= User-Agent: Thunderbird 2.0.0.23 (Windows/20090812) MIME-Version: 1.0 To: mint@lists.fishpool.fi Subject: Re: [MiNT] bug in gcc! References: <4B546F0D.3030601@freesbee.fr> <4B5585C1.5020400@freesbee.fr> <1e3f6d361001190600r60be65cexebd1bf7b1951c45f@mail.gmail.com> In-Reply-To: <1e3f6d361001190600r60be65cexebd1bf7b1951c45f@mail.gmail.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit 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: David Brownlee wrote: > It seems like a triple whammy - a.out, m68k *and* a very old version of gcc. - a.out is obsolete, but currently mandatory for our binutils patches. - m68k is still active for several OS including Linux, and the ColdFire is not obsolete. - our last gcc version is 4.4.2, which is the latest stable release. I personally want to stay up to date, to get the latest features and possible bugfixes (when not too specific). > Just a possibly relevant gcc comment - NetBSD is using gcc 4.1.3 for > 68000 and m68k (68020-60) on a bunch of platforms and feeding patches > back (though in ELF), m68k is not totally moribund in gcc-land :) Yes, NetBSD is still active. And especially, in the binutils there is official support for m68k a.out with NetBSD. So when I reported bugs, it was against that target, to maximize the chances they would be fixed. -- Vincent Rivière