From mint-bounce@lists.fishpool.fi  Thu Apr  8 14:20:52 2010
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=gamma;
        h=domainkey-signature:mime-version:received:in-reply-to:references
         :date:received:message-id:subject:from:to:cc:content-type;
        bh=4hIbRGFG9wmbvrVDMfa8HgBQ0pARjSrNnHdLniOut7w=;
        b=bgo1IpoHwYkYzHo63/McGR9dr8FVCnc+0ie3h09Gy9w1uAi0tsV0/HvSUqJoE4wVLw
         G9Q5Z4YP6Jn/Pzv9VsHX5Va+y2pBtIYyO5pOR/LFpvUWa4yZ21W79kmcGV3PE3OZFhCP
         m6z0jGBFb+eJjPbHXdJAd+2GucSCs+pTxP7zA=
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :cc:content-type;
        b=Yp3DpixGzm2tt+HpMoxFi1FMsgjTwVtxD1hmKx0T0kxkEXfj0q+ywPBVMVdH1lmacP
         Tv3aEIcTpeJb4mJQMeAJC2miXMDa/fyUy2hXT9WVmqGn+DW5cLlZ6aWmhQjW9edZj6cE
         UsAiydi7SGw6dFk2g2rrzGCDKsob+GZ3RAsI4=
MIME-Version: 1.0
In-Reply-To: <4BBE134B.9010400@freesbee.fr>
References: <1270663938.19190.1368.camel@jetpack.demon.co.uk>
	 <4BBDFF6B.8090401@freesbee.fr> <4BBE134B.9010400@freesbee.fr>
Date: Thu, 8 Apr 2010 20:18:39 +0200
Message-ID: <y2yc6533ef61004081118ybf743075uf829a224ee734351@mail.gmail.com>
Subject: Re: [MiNT] GCC upstream ??
From: Miro Kropacek <miro.kropacek@gmail.com>
To: =?ISO-8859-1?Q?Vincent_Rivi=E8re?= <vincent.riviere@freesbee.fr>
Cc: mint@lists.fishpool.fi
Content-Type: multipart/alternative; boundary=00151758aa6c4182320483bdb5ff
X-ecartis-version: Ecartis v1.0.0
Sender: mint-bounce@lists.fishpool.fi
Errors-to: mint-bounce@lists.fishpool.fi
X-original-sender: miro.kropacek@gmail.com
Precedence: bulk
List-help: <mailto:ecartis@lists.fishpool.fi?Subject=help>
List-unsubscribe: <mailto:mint-request@lists.fishpool.fi?Subject=unsubscribe>
List-Id: <mint.lists.fishpool.fi>
X-List-ID: <mint.lists.fishpool.fi>
List-subscribe: <mailto:mint-request@lists.fishpool.fi?Subject=subscribe>
List-owner: <mailto:tjhukkan@fishpool.fi>
List-post: <mailto:mint@lists.fishpool.fi>

--00151758aa6c4182320483bdb5ff
Content-Type: text/plain; charset=ISO-8859-1

>
> If there is no objection from the MiNT community, I'm going to continue
> that way. This means that the future unpatched binutils sources will
> integrate full MiNT support, with the exact same features as in my latest
> patch.
>
Cool! Many thanks for taking care about this, no more patches for us.

>
> If this is going to succeed (more likely), the next task will be to
> integrate the GCC patches. A totally different story.
>
Just out of interest, what problems you're facing here? I assumed your GCC
patches are clean and nice, i.e. same as with binutils.

-- 
MiKRO / Mystic Bytes
http://mikro.atari.org

--00151758aa6c4182320483bdb5ff
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div class=3D"gmail_quote"><blockquote class=3D"gmail_quote" style=3D"margi=
n:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">If there is no o=
bjection from the MiNT community, I&#39;m going to continue that way. This =
means that the future unpatched binutils sources will integrate full MiNT s=
upport, with the exact same features as in my latest patch.<br>
</blockquote><div>Cool! Many thanks for taking care about this, no more pat=
ches for us.</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .=
8ex;border-left:1px #ccc solid;padding-left:1ex;">
<br>
If this is going to succeed (more likely), the next task will be to integra=
te the GCC patches. A totally different story.<br></blockquote><div>Just ou=
t of interest, what problems you&#39;re facing here? I assumed your GCC pat=
ches are clean and nice, i.e. same as with binutils.</div>
<div><br></div></div>-- <br>MiKRO / Mystic Bytes<br><a href=3D"http://mikro=
.atari.org">http://mikro.atari.org</a><br>

--00151758aa6c4182320483bdb5ff--