From nobody Sat Apr 23 21:33:04 2022 X-Original-To: freebsd-hackers@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 8D7DB1996B4C for ; Sat, 23 Apr 2022 21:33:16 +0000 (UTC) (envelope-from joerg@bec.de) Received: from relay4-d.mail.gandi.net (relay4-d.mail.gandi.net [IPv6:2001:4b98:dc4:8::224]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4Km4JW0QyZz4qLN for ; Sat, 23 Apr 2022 21:33:14 +0000 (UTC) (envelope-from joerg@bec.de) Received: (Authenticated sender: joerg@bec.de) by mail.gandi.net (Postfix) with ESMTPSA id 7A193E0002 for ; Sat, 23 Apr 2022 21:33:06 +0000 (UTC) Date: Sat, 23 Apr 2022 23:33:04 +0200 From: Joerg Sonnenberger To: freebsd-hackers@freebsd.org Subject: Re: llvm & RTTI over shared libraries Message-ID: Mail-Followup-To: freebsd-hackers@freebsd.org References: List-Id: Technical discussions relating to FreeBSD List-Archive: https://lists.freebsd.org/archives/freebsd-hackers List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-hackers@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Rspamd-Queue-Id: 4Km4JW0QyZz4qLN X-Spamd-Bar: / Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=none (mx1.freebsd.org: domain of joerg@bec.de has no SPF policy when checking 2001:4b98:dc4:8::224) smtp.mailfrom=joerg@bec.de X-Spamd-Result: default: False [-0.70 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; FREEFALL_USER(0.00)[joerg]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MIME_GOOD(-0.10)[text/plain]; TO_DN_NONE(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[freebsd-hackers@freebsd.org]; AUTH_NA(1.00)[]; RCPT_COUNT_ONE(0.00)[1]; DMARC_NA(0.00)[bec.de]; NEURAL_HAM_SHORT(-0.63)[-0.630]; NEURAL_SPAM_LONG(0.03)[0.026]; MLMMJ_DEST(0.00)[freebsd-hackers]; R_SPF_NA(0.00)[no SPF record]; RCVD_COUNT_ZERO(0.00)[0]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:203476, ipnet:2001:4b98:dc4::/48, country:FR]; MID_RHS_MATCH_FROM(0.00)[] X-ThisMailContainsUnwantedMimeParts: N Am Tue, Apr 19, 2022 at 11:03:33PM -0700 schrieb Mark Millard: > Joerg Sonnenberger wrote on > Tue, 19 Apr 2022 21:49:44 UTC : > > > Am Thu, Apr 14, 2022 at 04:36:24PM +0000 schrieb jbo@insane.engineer: > >> > After some research I seem to understand that the way that RTTI is handled over shared library boundaries is different between GCC and LLVM. > >> > > I think you are running into the old problem that GCC thinks comparing > > types by name makes sense where as everyone else compares types by type > > pointer identity. > > Seems out of date for the GCC information . . . > > https://gcc.gnu.org/faq.html#dso reports: > > QUOTE > The new C++ ABI in the GCC 3.0 series uses address comparisons, rather than string compares, to determine type equality. > END QUOTE Compare that with the implementation in . Joerg