public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Tristan Gingold <gingold@adacore.com>
To: Gerald Pfeifer <gerald@pfeifer.com>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [Patch/RFC] SEH exceptions for Win64
Date: Wed, 25 Jul 2012 08:39:00 -0000	[thread overview]
Message-ID: <138BD038-E661-4916-B9BC-195C5406A153@adacore.com> (raw)
In-Reply-To: <76DF26FA-6064-401C-8EF3-0D80FFE18DAA@adacore.com>

Gerald,

it is ok ?

Tristan.

On Jul 19, 2012, at 12:15 PM, Tristan Gingold wrote:

> 
> On Jul 19, 2012, at 11:37 AM, Pedro Alves wrote:
> 
>> On 07/19/2012 08:30 AM, Tristan Gingold wrote:
>> 
>>> No regression on i386 GNU/Linux.
>>> Committed.
>> 
>> Nice.  Is this NEWS / docs --or wherever release notes are written-- worthy?
>> 
>> Something like this, borrowed from your own words:
>> 
>> On Win64, the compiler now emits SEH unwind info.  GCC exceptions now propagate
>> through any code, including code produced by MSVC.
> 
> To clarify, GCC emits SEH unwind info since 4.7, so I propose slightly modified words:
> 
> Index: htdocs/gcc-4.8/changes.html
> ===================================================================
> RCS file: /cvs/gcc/wwwdocs/htdocs/gcc-4.8/changes.html,v
> retrieving revision 1.6
> diff -c -r1.6 changes.html
> *** htdocs/gcc-4.8/changes.html	17 Jul 2012 19:47:31 -0000	1.6
> --- htdocs/gcc-4.8/changes.html	19 Jul 2012 10:15:13 -0000
> ***************
> *** 86,91 ****
> --- 86,97 ----
>      libraries.  This includes the system libraries and startup modules.</li>
>    </ul>
> 
> +   <ul>
> +     <li>On x86_64-mingw32, exceptions propagate through any code,
> +     including code produced by MSVC (the GCC runtime now uses SEH on
> +     this target)</li>
> +   </ul>
> + 
>  <!--
>  <h2>Documentation improvements</h2>
>  -->
> 

  parent reply	other threads:[~2012-07-25  8:39 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-13 14:13 Tristan Gingold
2012-07-16 18:53 ` Richard Henderson
2012-07-17  7:35   ` Tristan Gingold
2012-07-17 12:40     ` Richard Henderson
2012-07-17 12:53       ` Kai Tietz
2012-07-19  7:31         ` Tristan Gingold
2012-07-19  9:38           ` Pedro Alves
2012-07-19 10:15             ` Tristan Gingold
2012-07-19 10:19               ` Pedro Alves
2012-07-25  8:39               ` Tristan Gingold [this message]
2012-07-26  0:03                 ` Gerald Pfeifer
2012-07-19 16:55 ` Eric Botcazou
2012-07-20  7:22   ` Tristan Gingold

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=138BD038-E661-4916-B9BC-195C5406A153@adacore.com \
    --to=gingold@adacore.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=gerald@pfeifer.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).