From: JonY <10walls@gmail.com>
To: cygwin@cygwin.com
Subject: Re: Request update GCC
Date: Mon, 26 Jun 2017 01:11:00 -0000 [thread overview]
Message-ID: <7908d205-3321-410c-5009-e486ae556d90@gmail.com> (raw)
In-Reply-To: <3a4f8ce8-e76c-678c-c11c-e91366e57ec7@gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 465 bytes --]
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=66145
>>
>
> Would you mine testing GCC6? IIRC exception handling is broken in 6,
> which is why it is stuck in test.
>
> I suppose I can put gcc 6.3 in test soon.
>
>
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.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 858 bytes --]
next prev parent reply other threads:[~2017-06-26 1:11 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-25 2:22 Steven Penny
2017-06-25 4:03 ` JonY
2017-06-26 1:11 ` JonY [this message]
2017-06-26 19:27 ` Christian Franke
2017-06-28 23:14 ` JonY
2017-06-26 10:16 ` Marco Atzeri
2017-06-27 1:09 ` JonY
2017-06-27 11:33 ` Marco Atzeri
2017-06-28 2:22 ` Ken Brown
2017-06-28 11:34 ` Marco Atzeri
2017-08-10 1:10 ` Steven Penny
2017-08-13 4:19 ` JonY
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7908d205-3321-410c-5009-e486ae556d90@gmail.com \
--to=10walls@gmail.com \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).