DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:subject:to:references:from:message-id:date
	:mime-version:in-reply-to:content-type; q=dns; s=default; b=P6Xq
	2njutBJK0WxRnXyyZuZkPt6ZPMsZq4o6azaNH0AcArTTm8CuxNQpIIfZJ/1+PG+U
	9ZaMONDHAHy9pY/U6/AhQ/x1fb3bH41sqZQhwNZBe3/tSZFZbwnCUcflq9FVbFxJ
	F6toDabco7Q6Yha0kTibEBtnphdy04cR3+ICxms=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Subject: Re: Request update GCC
To: cygwin AT cygwin DOT com
References: <594f1e45 DOT 14119d0a DOT 73dda DOT b6f9 AT mx DOT google DOT com> <3a4f8ce8-e76c-678c-c11c-e91366e57ec7 AT gmail DOT com>
From: JonY <10walls AT gmail DOT com>
Message-ID: <7908d205-3321-410c-5009-e486ae556d90@gmail.com>
Date: Mon, 26 Jun 2017 01:10:43 +0000
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <3a4f8ce8-e76c-678c-c11c-e91366e57ec7@gmail.com>
Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="bCBTRPjSkk9RKGlrOTXeoI7BXr25o5wf2"

--bCBTRPjSkk9RKGlrOTXeoI7BXr25o5wf2
Content-Type: multipart/mixed; boundary="gc9FKcUfgfEqcrDPINKItwprxsSNeicGk";
 protected-headers="v1"
From: JonY <10walls AT gmail DOT com>
To: cygwin AT cygwin DOT com
Message-ID: <7908d205-3321-410c-5009-e486ae556d90 AT gmail DOT com>
Subject: Re: Request update GCC
References: <594f1e45 DOT 14119d0a DOT 73dda DOT b6f9 AT mx DOT google DOT com>
 <3a4f8ce8-e76c-678c-c11c-e91366e57ec7 AT gmail DOT com>
In-Reply-To: <3a4f8ce8-e76c-678c-c11c-e91366e57ec7 AT gmail DOT com>


--gc9FKcUfgfEqcrDPINKItwprxsSNeicGk
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable

On 06/25/2017 04:03 AM, JonY wrote:
>>
>> GCC 5 is starting to show its age:
>>
>> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D66145
>>
>=20
> Would you mine testing GCC6? IIRC exception handling is broken in 6,
> which is why it is stuck in test.
>=20
> I suppose I can put gcc 6.3 in test soon.
>=20
>=20

Woops, looks like gcc-6.3 is already in test.

Taking a closer look at the bug report, we're still using the old C++
ABI, so we're unaffected.


--gc9FKcUfgfEqcrDPINKItwprxsSNeicGk--

--bCBTRPjSkk9RKGlrOTXeoI7BXr25o5wf2
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQJGBAEBCAAwFiEE5QrdnbBX9Ppk4bbPcTtf4pwUXUUFAllQXxQSHDEwd2FsbHNA
Z21haWwuY29tAAoJEHE7X+KcFF1FZR4QAIsWP0gkr0WH1QaK2ZmkwG0/aHyKZRai
4wnfPFJWWrLup+lKOz2G5u2yXwi3RePULrKAkBMoKnc/hJ+Cgq1SCDo5/ESdwg4u
loUWu7dU9ODSFsOmh4Hg6Xxc4bRnQYQWsZyjNexbFGOU5OFmpH4E5pT8Gu5ipTbk
THjpaRsJYaFLP85gt+WsOcPQ96ZavbV4iK6yyz4LFHdmToU9oyGuYN/2uGO8Wfjw
YHCJ5huvlycUI9eIiM3Q4y+qI5xwZVm/L5AVEGg8IBJlX7BGnEm06D9RVlX5woTB
hFiN1m79cr/Xb5XsbXEs9DnAmkoRX8pBdTpUbceNb7GKqKNnujDZZ3B652osM6Bj
75oh6OnCyfV/kOyFnQN0+NxmtnlDN0iaJuaIwJzBWlIkBNLeI+DCteNNb5gTbhon
b93roZjbRDcpZ72vkbCvv/vWtzPZ7cXfYy1DbFuLCI4uS/XYcXQjVjy6JGs47KAv
t6FelXZqEm1V946m+oYQjhK3rkWKkT19Iqon2x+Ur7rlURs4iuwL+oEePTzFIO9v
YsnCxz9OYOMXQS30XAD2y9KQRkKlbOF/vC3GNk35E+BKsI9d2JJE03wtDaE9Zt0f
TR4rurThR/IQQ3Gbix9/kq/jDXGYXSqAfqrFEPgtSJFDEuv/Vik2u4RrV74kL2an
3n03lF5qLxt6
=rgCL
-----END PGP SIGNATURE-----

--bCBTRPjSkk9RKGlrOTXeoI7BXr25o5wf2--