From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.129.124]) by sourceware.org (Postfix) with ESMTPS id 9977D3858C20 for ; Thu, 8 Jun 2023 14:04:00 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org 9977D3858C20 Authentication-Results: sourceware.org; dmarc=pass (p=none dis=none) header.from=redhat.com Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=redhat.com DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1686233040; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=tibNULsPik6Di6M20M7k4CxkTDJc3zvSLiyv1uE5PLA=; b=W+nkKueJnvLaYOl4/p2FM2HrUmjfmLnwV/Yd+7i4EQLgM76EEHKv3LCbvk+4DscxxI2tQU YEwiUdjuFKeT5AUaQWz8Z/jG29L1h8W029meXo9scKFBPArOhhkDnR3YugmdWIqGpuvmwQ pAxWzR5vThtdQxH4EkQjARoYI/ygloo= Received: from mail-il1-f199.google.com (mail-il1-f199.google.com [209.85.166.199]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_256_GCM_SHA384) id us-mta-227-eVMqMhgRPS-9ldQZ53IUTQ-1; Thu, 08 Jun 2023 10:03:52 -0400 X-MC-Unique: eVMqMhgRPS-9ldQZ53IUTQ-1 Received: by mail-il1-f199.google.com with SMTP id e9e14a558f8ab-33bdb682a1fso4414455ab.0 for ; Thu, 08 Jun 2023 07:03:42 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1686233022; x=1688825022; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=tibNULsPik6Di6M20M7k4CxkTDJc3zvSLiyv1uE5PLA=; b=MfBwLjBE0qmmZG4fAtRrUTog1aMDMYUQtkEzJ3bIiNEV3ElhX4my2C1XnkEjf/q1o+ lsCeFjFWDlALEUxBEbsiNouEhNSJleyi1CCSRvblArTmZ9t3Zwu5h3x+PvVNr4eUGL7J Q/IuFNcp6RW03w6HjSVfUHM42MSRk/FRuUNdb9Gg/ItRLZLvYsiwpAMgW+t7LpqZ9wKA vBjAAF5LbUOihX3uZUq1bUN/qZZtWi8G4qM8A4KMoNja8iDtSPORHd2J+AAyk/1ARIvz a53tuNdlDGWqJpVui/ci2CQ6FQ0I223Zkxfz1dtihUE/5pnIrEGlIzmLwOAAaHQNagfu 5KFw== X-Gm-Message-State: AC+VfDyoArH8lNgdj2ruAVKH/Dj1B/S4AHp7zCRuDKX9IEZpfwkpHIH4 tcUACUm/peE1q4Ts0QxT/hL/+OJ9zYVqhybqEnCwtMOVRvvSHOPTjCxseVIC2lDaitXpuzVK5Rr VTmsLCABsARmE3LWFexBvclAWEu4E6wwW4Q== X-Received: by 2002:a92:c909:0:b0:33d:11cd:c7b2 with SMTP id t9-20020a92c909000000b0033d11cdc7b2mr6590867ilp.24.1686233022125; Thu, 08 Jun 2023 07:03:42 -0700 (PDT) X-Google-Smtp-Source: ACHHUZ6OdIjDs+EDotOaCrZ2sjgVcGQhKtu9rnS4oYKl/IqtN/kwN69IbSgyVxqEUuU0Q/PYeX5msK77OCx1/MUszlw= X-Received: by 2002:a92:c909:0:b0:33d:11cd:c7b2 with SMTP id t9-20020a92c909000000b0033d11cdc7b2mr6590851ilp.24.1686233021846; Thu, 08 Jun 2023 07:03:41 -0700 (PDT) MIME-Version: 1.0 References: <20230524185559.1285583-1-jason@redhat.com> In-Reply-To: From: Jason Merrill Date: Thu, 8 Jun 2023 10:03:30 -0400 Message-ID: Subject: Re: [PATCH RFC] c++: use __cxa_call_terminate for MUST_NOT_THROW [PR97720] To: Jonathan Wakely Cc: gcc-patches@gcc.gnu.org, libstdc++@gcc.gnu.org X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: multipart/alternative; boundary="00000000000046b55805fd9eb86a" X-Spam-Status: No, score=-16.3 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,HTML_MESSAGE,RCVD_IN_DNSWL_NONE,SPF_HELO_NONE,SPF_NONE,TXREP,T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on server2.sourceware.org List-Id: --00000000000046b55805fd9eb86a Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Thu, Jun 8, 2023 at 9:13=E2=80=AFAM Jonathan Wakely = wrote: > > On Fri, 26 May 2023 at 10:58, Jonathan Wakely wrote: > >> >> >> On Wed, 24 May 2023 at 19:56, Jason Merrill via Libstdc++ < >> libstdc++@gcc.gnu.org> wrote: >> >>> Middle-end folks: any thoughts about how best to make the change >>> described in >>> the last paragraph below? >>> >>> Library folks: any thoughts on the changes to __cxa_call_terminate? >>> >> >> I see no harm in exporting it (with the adjusted signature). The "looks >> standard but isn't" name is a little unfortunate, but not a big deal. >> > > Jason, do you have any objection to exporting __cxa_call_terminate for GCC > 13.2 as well, even though the FE won't use it? > That sounds fine. Jason --00000000000046b55805fd9eb86a--