public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: JonY <10walls@gmail.com>
To: cygwin@cygwin.com
Subject: Re: gcc-6.3.0-1 regression: libstdc++6 DLL breaks exception handling
Date: Tue, 07 Feb 2017 10:04:00 -0000	[thread overview]
Message-ID: <dcea951e-96f2-b592-4804-1c58abf84a83@gmail.com> (raw)
In-Reply-To: <6a80a46a-8de9-5d28-f7ef-897a53159603@t-online.de>


[-- Attachment #1.1: Type: text/plain, Size: 240 bytes --]

On 01/26/2017 10:30 AM, Christian Franke wrote:
> After upgrading to gcc test version 6.3.0-1, C++ exception handling is
> broken if DLL version of new libstdc++6 is used.
> 

Noted, I'll consider the test version broken for now.



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 829 bytes --]

  reply	other threads:[~2017-02-07 10:04 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-26 10:31 Christian Franke
2017-02-07 10:04 ` JonY [this message]
2017-02-07 15:27   ` Christian Franke

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=dcea951e-96f2-b592-4804-1c58abf84a83@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).