From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id F10D9389367F; Wed, 22 Jul 2020 13:56:23 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org F10D9389367F DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1595426183; bh=S+p9E0oy11GMQBADRvSGhBQ0vx8Un2MfR+rx5XgQFC0=; h=From:To:Subject:Date:In-Reply-To:References:From; b=eEl5VbHfmSKk5eA1SwCneK1APvAbRqePagfsiIOo2GKLGIuvv9SXh0NWtvbr50grX SknO/dKCvlDfUkF4C9kk+/BIOPX3ZV0CNqYE1J8CHpyqitX2dZpQyQ5Dy0a6MPtyoV ABsC5dwt3YyIrJyQvMCeuQ/9hClreY3FX7yrFRAU= From: "redi at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug other/42540] c++ error message [vtable undefined] is unhelpful Date: Wed, 22 Jul 2020 13:56:23 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: other X-Bugzilla-Version: 4.5.0 X-Bugzilla-Keywords: diagnostic X-Bugzilla-Severity: enhancement X-Bugzilla-Who: redi at gcc dot gnu.org X-Bugzilla-Status: ASSIGNED X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: jyasskin at gmail dot com X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: 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 X-BeenThere: gcc-bugs@gcc.gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gcc-bugs mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 22 Jul 2020 13:56:24 -0000 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D42540 --- Comment #12 from Jonathan Wakely --- (In reply to Zhihao Yuan from comment #11) > 1. Adjust the error message to say, "The first non-inline, non-pure funct= ion > may not have a definition in ." That error comes from the linker. The linker is not part of GCC, so this is= the wrong place to ask for linker changes. > 2. Add extra information to name the key function, and pass it to the > linker, generate an error message to match MSVC's quality. That's what comment 7 suggested. Comment 10 links to the response to that.=