From: Stephan Bergmann <sbergman@redhat.com>
To: gcc@gcc.gnu.org
Subject: Re: C++: Letting compiler know asm block can call function that can throw?
Date: Thu, 29 Mar 2012 15:10:00 -0000 [thread overview]
Message-ID: <4F747B4A.5040905@redhat.com> (raw)
In-Reply-To: <4F746DB5.2080607@redhat.com>
On 03/29/2012 04:12 PM, Andrew Haley wrote:
> On 03/29/2012 02:59 PM, Michael Matz wrote:
>> Actually, with -fnon-call-exceptions volatile asms are already supposed to
>> be throwing. It's just that this got lost with tree-ssa. With the patch
>> and -fnon-call-exceptions a simple "__asm__ volatile (...)" is regarded as
>> possibly throwing.
>>
>> Without -fnon-call-exceptions some parser changes would be required. How
>> about "asm throw (...)" ?
>
> Is there any point? I would have thought that -fnon-call-exceptions was
> exactly what you need.
But it looks wrong to me to have to mark the complete compilation unit
for something that should only affect a single asm declaration. (Also,
having to specify -fnon-call-exceptions "externally," on the command
line, is somewhat awkward.)
Stephan
next prev parent reply other threads:[~2012-03-29 15:10 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-29 7:05 Stephan Bergmann
2012-03-29 7:44 ` Jakub Jelinek
2012-03-29 8:48 ` Stephan Bergmann
2012-03-29 9:16 ` Richard Guenther
2012-03-29 12:51 ` Stephan Bergmann
2012-03-29 13:59 ` Michael Matz
2012-03-29 14:12 ` Andrew Haley
2012-03-29 15:10 ` Stephan Bergmann [this message]
2012-03-29 15:43 ` Michael Matz
2012-03-29 20:38 ` Eric Botcazou
2012-03-30 8:23 ` Richard Guenther
2012-03-29 16:14 ` Richard Henderson
2012-03-29 17:16 ` Jan Hubicka
2012-03-29 18:34 ` Richard Henderson
2012-03-30 8:19 ` Richard Guenther
2012-03-30 12:21 ` Jan Hubicka
2012-03-30 12:23 ` Richard Guenther
2012-03-30 15:46 ` Jan Hubicka
2012-04-02 14:08 ` Michael Matz
2012-04-02 14:17 ` Jakub Jelinek
2012-04-02 16:04 ` Michael Matz
2012-04-16 20:01 ` Hans-Peter Nilsson
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=4F747B4A.5040905@redhat.com \
--to=sbergman@redhat.com \
--cc=gcc@gcc.gnu.org \
/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).