From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 129813 invoked by alias); 31 May 2017 08:32:34 -0000 Mailing-List: contact gcc-help-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-help-owner@gcc.gnu.org Received: (qmail 129799 invoked by uid 89); 31 May 2017 08:32:34 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-1.9 required=5.0 tests=BAYES_00,RP_MATCHES_RCVD,SPF_HELO_PASS autolearn=ham version=3.3.2 spammy=Ltd, ltd X-HELO: mx1.redhat.com Received: from mx1.redhat.com (HELO mx1.redhat.com) (209.132.183.28) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Wed, 31 May 2017 08:32:33 +0000 Received: from smtp.corp.redhat.com (int-mx06.intmail.prod.int.phx2.redhat.com [10.5.11.16]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id 7280B15D9 for ; Wed, 31 May 2017 08:32:35 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mx1.redhat.com 7280B15D9 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@redhat.com DKIM-Filter: OpenDKIM Filter v2.11.0 mx1.redhat.com 7280B15D9 Received: from zebedee.pink (unknown [10.40.205.45]) by smtp.corp.redhat.com (Postfix) with ESMTP id BD3A15C542; Wed, 31 May 2017 08:32:34 +0000 (UTC) Subject: Re: Exception handling To: gcc-help@gcc.gnu.org References: From: Andrew Haley Message-ID: Date: Wed, 31 May 2017 08:32:00 -0000 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.1.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-IsSubscribed: yes X-SW-Source: 2017-05/txt/msg00222.txt.bz2 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. EAC8 43EB D3EF DB98 CC77 2FAD A5CD 6035 332F A671