From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wr1-x436.google.com (mail-wr1-x436.google.com [IPv6:2a00:1450:4864:20::436]) by sourceware.org (Postfix) with ESMTPS id EBD773856241 for ; Fri, 6 May 2022 06:55:41 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org EBD773856241 Received: by mail-wr1-x436.google.com with SMTP id e24so8731315wrc.9 for ; Thu, 05 May 2022 23:55:41 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=VEDvF5EEGyD+hB0oLI7FRwcLmq4/saKpdNF1l1XP3do=; b=B2n30wsFql0NU16Rp+ficPy5YIg2waydonm/n3ub1Z5pq6r4P0i2Ardo1PEpaojTR3 zAsy8rE+SVFrxwqFCPGI44JlsVMbDhdnaT/ZE9RC6msCKhS+clEEnIv/1u2o1yx8iWDx UI5HcySVzcUpbF1y9xr1f6gP1stl6giC3YI+JUiU9dAfNtPyx2sIkZC3+ccX5MCTxMSn SqifaRZU//P62kRuuOfHR8FtQiwCJ4GcMMPcAYlzKNIMtMH+qJZ7WcM5bZ4mLiZbwNw0 uqskmTA+uGoV5Bv/gYpq4bfj1af2ufgMPCOiHy/CChFVnP0PAbcVdc8LydE32JFFVh9s pr8A== X-Gm-Message-State: AOAM532cUaImNsYKqZJubO9LqB3xoB4VKNN55U3Qtvf5YuNgIZixd13I FURs51iod7SmtR2neeWw7nrxOtPcLkKQuI6YOYs= X-Google-Smtp-Source: ABdhPJzR2P+KqkFZbfI7D47O1E2rZ9OadufDdFNS+4ExOyH9dq2uaqqxLD4zCAC54uJiEbtjKYmVbEpZWv2nkZP8aA4= X-Received: by 2002:a05:6000:1687:b0:20c:7de9:feca with SMTP id y7-20020a056000168700b0020c7de9fecamr1432528wrd.221.1651820140618; Thu, 05 May 2022 23:55:40 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Jonathan Wakely Date: Fri, 6 May 2022 07:55:28 +0100 Message-ID: Subject: Re: [PATCH] libstdc++: fix pointer type exception catch [PR105387] To: Jakob Hasse Cc: "libstdc++" , Rocha Euripedes , Ivan Grokhotkov X-Spam-Status: No, score=-1.0 required=5.0 tests=BAYES_00, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, FREEMAIL_FROM, HTML_MESSAGE, RCVD_IN_DNSWL_NONE, SPF_HELO_NONE, SPF_PASS, TXREP, T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.4 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on server2.sourceware.org Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.29 X-BeenThere: libstdc++@gcc.gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Libstdc++ mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 06 May 2022 06:55:43 -0000 On Fri, 6 May 2022, 02:43 Jakob Hasse, wrote: > I'll re-run tests on current master. > > About the pointer-to-member issue: You're right, I missed that. I don't > know a solution so far. Should I continue preparing the patch anyway, as a > temporary solution? > Yes, please do. I think losing the ability to catch pointers to member via qualification conversions might be a necessary consequence of avoiding undefined behaviour and crashes in other cases. It only affects people building libstdc++ without RTTI anyway, which is unusual. > If so, I'll adjust the patch according to the comments earlier > (formalities, coding rules, etc.). > > Does GCC's libstdc++-v3 have some kind of "errata"? > No, bugzilla serves that purpose, or the release notes for larger changes. doc/xml/manual/evolution.xml documents user-visible API changes, but this doesn't qualify, it's just a bug fix. doc/xml/manual/intro.xml documents implemented defects fixed in the C++ standard itself.