This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: C++: Letting compiler know asm block can call function that can throw?

From: Eric Botcazou <ebotcazou at adacore dot com>
To: Michael Matz <matz at suse dot de>
Cc: gcc at gcc dot gnu dot org, Andrew Haley <aph at redhat dot com>
Date: Thu, 29 Mar 2012 22:36:27 +0200
Subject: Re: C++: Letting compiler know asm block can call function that can throw?
References: <4F7409B9.2010407@redhat.com> <4F746DB5.2080607@redhat.com> <Pine.LNX.4.64.1203291741080.25409@wotan.suse.de>

> non-call-exceptions is a relatively big hammer.  It marks _all_
> non-trivial instructions as throwing.

The "all" goes against the "relatively" here, and "relatively" is more correct.
Not all non-trivial instructions are marked as throwing, e.g. loads and stores 
from/to the stack aren't.

-- 
Eric Botcazou

References:
- C++: Letting compiler know asm block can call function that can throw?
  - From: Stephan Bergmann
- Re: C++: Letting compiler know asm block can call function that can throw?
  - From: Andrew Haley
- Re: C++: Letting compiler know asm block can call function that can throw?
  - From: Michael Matz

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]