Re: LTO ltrans name mangling in GCC 4.8.2

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

To: Lassi Niemistö <lassi.niemisto@xxxxxxxxxx>
Subject: Re: LTO ltrans name mangling in GCC 4.8.2
From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
Date: Fri, 1 Sep 2017 09:41:32 +0100
Cc: Xi Ruoyao <ryxi@xxxxxxxxxxxxxxxxx>, "gcc-help@xxxxxxxxxxx" <gcc-help@xxxxxxxxxxx>
In-reply-to: <b258804abb6643478e4edb42acfa46a1@EDB3.wapice.localdomain>
References: <a93fabe6769646399864db467593dae3@EDB3.wapice.localdomain> <1504186346.8573.1.camel@stu.xidian.edu.cn> <b258804abb6643478e4edb42acfa46a1@EDB3.wapice.localdomain>

On 1 September 2017 at 05:42, Lassi Niemistö wrote:
>> I don't know if we can do this in GCC 4.8.2.  With GCC 7.2 these names become "<artifical>".
>
> Another reply says it is fixed in 4.8.5, which one should I believe? Any bug tracker link?

The replies are not contradictory. It was fixed in 4.8.5, and still
remains fixed in 7.2

References:
- LTO ltrans name mangling in GCC 4.8.2
  - From: Lassi Niemistö
- Re: LTO ltrans name mangling in GCC 4.8.2
  - From: Xi Ruoyao
- RE: LTO ltrans name mangling in GCC 4.8.2
  - From: Lassi Niemistö

Prev by Date: Re: LTO ltrans name mangling in GCC 4.8.2
Next by Date: Problem with linking step
Previous by thread: RE: LTO ltrans name mangling in GCC 4.8.2
Next by thread: Problem with linking step
Index(es):
- Date
- Thread

[Index of Archives] [Linux C Programming] [Linux Kernel] [eCos] [Fedora Development] [Fedora Announce] [Autoconf] [The DWARVES Debugging Tools] [Yosemite Campsites] [Yosemite News] [Linux GCC]

Powered by Linux