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.133.124]) by sourceware.org (Postfix) with ESMTP id 8A0DB3858028 for ; Mon, 12 Apr 2021 18:45:50 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org 8A0DB3858028 Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com [209.132.183.4]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-414-1TG_Yh_PPI2fEyJWRmmNBQ-1; Mon, 12 Apr 2021 14:45:48 -0400 X-MC-Unique: 1TG_Yh_PPI2fEyJWRmmNBQ-1 Received: from smtp.corp.redhat.com (int-mx07.intmail.prod.int.phx2.redhat.com [10.5.11.22]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id CEFD2186833A; Mon, 12 Apr 2021 18:45:47 +0000 (UTC) Received: from theo.uglyboxes.com (ovpn-118-131.rdu2.redhat.com [10.10.118.131]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 57258100AE4E; Mon, 12 Apr 2021 18:45:47 +0000 (UTC) Subject: Re: Expected output of gdb.cp/no-dmgl-verbose.exp To: Luis Machado , "gdb@sourceware.org" References: <3de907e5-c711-ab80-8b27-f7c13fbde7ec@linaro.org> From: Keith Seitz Message-ID: <39eb19e5-d1fd-4997-60e0-e9835fd1d090@redhat.com> Date: Mon, 12 Apr 2021 11:45:46 -0700 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.7.0 MIME-Version: 1.0 In-Reply-To: <3de907e5-c711-ab80-8b27-f7c13fbde7ec@linaro.org> X-Scanned-By: MIMEDefang 2.84 on 10.5.11.22 X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-7.1 required=5.0 tests=BAYES_00, DKIMWL_WL_HIGH, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, NICE_REPLY_A, RCVD_IN_DNSWL_LOW, RCVD_IN_MSPIKE_H4, RCVD_IN_MSPIKE_WL, SPF_HELO_NONE, SPF_PASS, TXREP autolearn=ham autolearn_force=no version=3.4.2 X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on server2.sourceware.org X-BeenThere: gdb@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gdb mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Apr 2021 18:45:51 -0000 On 4/12/21 11:16 AM, Luis Machado via Gdb wrote: > I'm trying to determine why this particular test is failing (for both > aarch64-linux and x86_64-linux on Ubuntu 18.04/20.04) and what the > expected outcome is. > > In my case, the only symbol I see for function "f" is the following: > > "f(std::__cxx11::basic_string, > std::allocator >)" > > There is no "f(std::string)" nor "f(std::basic_string std::char_traits, std::allocator >)" symbol. > Wow, such a long time ago! IIRC... This test was written to ensure that "std::string" was used instead of "std::basic_string<...>" (which is now called something else again). Something about "that's what nm and other tools tell users, so we should not mention the symbol's real (linkage) name, either." The "no-dmgl-verbose" refers to the DMGL_VERBOSE option of the demangler, which does this. There is even special logic in our typedef-replacing machinery to enforce this. [NOTE: `ignore_typedefs' in cp-support.c is also "out- of-date" wrt to this naming change. So none of that has likely been "working" for many years, but then at very quick glance, "nm -C" doesn't do this anymore, either.] I was against it then, so I certainly do not mind getting rid of this test or limiting it to C++ installations that typedef the "older" std::basic_string<...> to std::string. Keith