linux/amd64, but I did on linux/ppc64le and
> > I don't think it's a ppc-only bug.
> >
> > Clément
> > ________
> > From: Ian Lance Taylor
> > Sent: Wednesday, December 2, 2020 4:55 PM
> > To: CHIGOT, CLEMENT
> > Cc:
; > I didn't try to reproduce it on linux/amd64, but I did on linux/ppc64le and
> > I don't think it's a ppc-only bug.
> >
> > Clément
> > ________
> > From: Ian Lance Taylor
> > Sent: Wednesday, December 2, 2020 4:55 PM
this problem.
Ian
>
> From: CHIGOT, CLEMENT
> Sent: Wednesday, December 2, 2020 5:14 PM
> To: Ian Lance Taylor
> Cc: gcc-patches@gcc.gnu.org ; David Edelsohn
>
> Subject: Re: [PATCH] gcc: handle double quotes in symbol name during
> stabstrings gener
Ian Lance Taylor
Cc: gcc-patches@gcc.gnu.org ; David Edelsohn
Subject: Re: [PATCH] gcc: handle double quotes in symbol name during
stabstrings generation
Hi Ian,
Here is the test case.
If you're compiling with -gstabs you should have a line looking like:
.stabs "type.
c-patches@gcc.gnu.org ; David Edelsohn
Subject: Re: [PATCH] gcc: handle double quotes in symbol name during
stabstrings generation
Caution! External email. Do not open attachments or click links, unless this
email comes from a known sender and you know the content is safe.
On Wed, Dec 2, 202
On Wed, Dec 2, 2020 at 4:24 AM CHIGOT, CLEMENT wrote:
>
> Since the new gccgo mangling scheme, libgo compilation is broken on AIX (or
> in Linux with -gstabs) because of a type symbol having a " in its name. I've
> made a patch (see attachment) in order to fix stabstring generation, because,
>
Hi Ian
Since the new gccgo mangling scheme, libgo compilation is broken on AIX (or in
Linux with -gstabs) because of a type symbol having a " in its name. I've made
a patch (see attachment) in order to fix stabstring generation, because, IMO,
it should be handled anyway.
However, it happens onl
