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?


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


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