From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <sourceware-bugzilla@sourceware.org>
Received: by sourceware.org (Postfix, from userid 48)
	id 4F639385B512; Mon,  2 Oct 2023 09:14:36 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 4F639385B512
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org;
	s=default; t=1696238076;
	bh=Ar8971FzRHpQBK47eevbLgJr9enAaYFL8Z53RzcLE/I=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=OVKkGp1N8zCbi4YOMkXxJXHdsN1ocvqOJ0O6Gsfv0OcdUtphrGQ8ZFnrF/TZwu5U1
	 raH/SFbgQE0I3mXgtOdloqKpRFN0eD+wCsVhPleUw1omyxgcyWHmQkezUqRlXjAq3T
	 I7ei+PhXn1tQXggdPSmdKAqMbRjBqBV1wrRyxQZE=
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug go/27238] [gcc-11] FAIL: gdb.go/package.exp: setting breakpoint
 at package2.Foo
Date: Mon, 02 Oct 2023 09:14:34 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gdb
X-Bugzilla-Component: go
X-Bugzilla-Version: HEAD
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: normal
X-Bugzilla-Who: vries at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at sourceware dot org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-27238-4717-Xg8gZtiRja@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-27238-4717@http.sourceware.org/bugzilla/>
References: <bug-27238-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
List-Id: <gdb-prs.sourceware.org>

https://sourceware.org/bugzilla/show_bug.cgi?id=3D27238

--- Comment #8 from Tom de Vries <vries at gcc dot gnu.org> ---
This is about supporting v3 mangling, introduced in gcc 11:
...
commit a01dda3c23b836754814fab1cab949a1bbc641e8
Author: Ian Lance Taylor <iant@golang.org>
Date:   Mon Nov 16 20:06:53 2020 -0800

    compiler, libgo: change mangling scheme

    Overhaul the mangling scheme to avoid ambiguities if the package path
    contains a dot. Instead of using dot both to separate components and
    to mangle characters, use dot only to separate components and use
    underscore to mangle characters.

    For golang/go#41862

    Reviewed-on: https://go-review.googlesource.com/c/gofrontend/+/271726
...

Difference in style:
...
+       // Original mangling: go.l__ufer.Run
+       // Mangling v2: go.l..u00e4ufer.Run
+       // Mangling v3: go_0l_u00e4ufer.Run
...

Explained in more detail in
https://github.com/golang/go/issues/41862#issuecomment-707244103 (second pa=
th
case was chosen, AFAICT).

--=20
You are receiving this mail because:
You are on the CC list for the bug.=