This is the mail archive of the
gcc-help@gcc.gnu.org
mailing list for the GCC project.
Re: Exception handling
- From: Andrew Haley <aph at redhat dot com>
- To: gcc-help at gcc dot gnu dot org
- Date: Wed, 31 May 2017 09:32:33 +0100
- Subject: Re: Exception handling
- Authentication-results: sourceware.org; auth=none
- Authentication-results: ext-mx05.extmail.prod.ext.phx2.redhat.com; dmarc=none (p=none dis=none) header.from=redhat.com
- Authentication-results: ext-mx05.extmail.prod.ext.phx2.redhat.com; spf=pass smtp.mailfrom=aph at redhat dot com
- Dkim-filter: OpenDKIM Filter v2.11.0 mx1.redhat.com 7280B15D9
- Dmarc-filter: OpenDMARC Filter v1.3.2 mx1.redhat.com 7280B15D9
- References: <VI1PR07MB31810694A9E69AA74DB08AF4E9F30@VI1PR07MB3181.eurprd07.prod.outlook.com>
On 29/05/17 10:00, Flis, Przemyslaw (Nokia - PL/Wroclaw) wrote:
> as far as I know, the way of handling exceptions "under the hood" is
> not defined in C++ standard. In "Technical report on C++
> performance" from 2008, I've found two main approaches to exception
> handling - so called "code" and "table" approach. Is there any way
> to determine which is used by gcc compiler?
I've never seen anything except "table".
> Does it depend on platform (i.e. ARM, x86 etc.) or compiler version?
It depends on the processor-speific ABI, which is defined by the
operating system. For example,
http://refspecs.linuxfoundation.org/elf/x86_64-abi-0.95.pdf
at
http://refspecs.linuxfoundation.org/
--
Andrew Haley
Java Platform Lead Engineer
Red Hat UK Ltd. <https://www.redhat.com>
EAC8 43EB D3EF DB98 CC77 2FAD A5CD 6035 332F A671