From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 5AAD53858C3A; Fri, 22 Sep 2023 01:12:16 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 5AAD53858C3A DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1695345136; bh=hT3/DSLxg4oS8KdbAFo6oTdwPV7DMXY1J/kkWA3fY/I=; h=From:To:Subject:Date:In-Reply-To:References:From; b=o9GMU9bgw+onauUR7uFSeb0fNuZH+M8FpyrFVy0Upy5y/jAF50KgwyHeZS5CmDX1w 4gfc6/8uQ6PVUFCKmw+ZeBxAAjW4MkQ2CoWxUto/H2g0GH9VdRERUb99DNIQQ/hBN0 Ayl3yxR2bM/evTY4G9vByEYimz8YLm+Zz+zw5E40= From: "pinskia at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/111531] Bound member function with multiple inheritance documentation should be clearer Date: Fri, 22 Sep 2023 01:12:15 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: c++ X-Bugzilla-Version: 13.2.0 X-Bugzilla-Keywords: documentation X-Bugzilla-Severity: enhancement X-Bugzilla-Who: pinskia at gcc dot gnu.org X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: short_desc everconfirmed bug_severity cf_reconfirmed_on bug_status Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 List-Id: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D111531 Andrew Pinski changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|Bound member function |Bound member function with |(-Wno-pmf-conversions) with |multiple inheritance |multiple inheritance |documentation should be | |clearer Ever confirmed|0 |1 Severity|normal |enhancement Last reconfirmed| |2023-09-22 Status|UNCONFIRMED |NEW --- Comment #2 from Andrew Pinski --- "the PMF needs to store information about how to adjust the =E2=80=98this= =E2=80=99 pointer," And then it says: "you can extract the pointer to the function that would be called for a giv= en object/PMF pair and call it directly inside the inner loop, to save a bit of time." Meaning the specifically a Bound member function loses the information on h= ow to adjust the this pointer and just contains a pointer to the function rath= er than anything else. That is why I said this is just a documentation issue of explaining this in more clearer langauge.=