On 07/24/2011 08:09 PM, H.J. Lu wrote:
On Sun, Jul 24, 2011 at 7:03 PM, H.J. Lu wrote:
On Mon, Jul 11, 2011 at 10:45 AM, Sandra Loosemore
wrote:
2011-06-17 Sandra Loosemore
gcc/
* configure.ac (demangler_in_ld): Default to yes.
* configure: Regenerated.
* collect2.c (main
On Sun, Jul 24, 2011 at 7:03 PM, H.J. Lu wrote:
> On Mon, Jul 11, 2011 at 10:45 AM, Sandra Loosemore
> wrote:
>> Ping?
>>
>> http://gcc.gnu.org/ml/gcc-patches/2011-06/msg01368.html
>>
>>> We had a bug report from a customer that the linker was ignoring the
>>> --demangle and --no-demangle options
On Mon, Jul 11, 2011 at 10:45 AM, Sandra Loosemore
wrote:
> Ping?
>
> http://gcc.gnu.org/ml/gcc-patches/2011-06/msg01368.html
>
>> We had a bug report from a customer that the linker was ignoring the
>> --demangle and --no-demangle options when generating map files.
>> Moreover, it was failing in
OK in the absence of middle-end or build-system maintainer objections
within 72 hours.
--
Joseph S. Myers
jos...@codesourcery.com
Ping?
http://gcc.gnu.org/ml/gcc-patches/2011-06/msg01368.html
We had a bug report from a customer that the linker was ignoring the
--demangle and --no-demangle options when generating map files.
Moreover, it was failing in a host-dependent way; on Windows hosts,
it was always emitting demangled
Ping?
http://gcc.gnu.org/ml/gcc-patches/2011-06/msg01368.html
We had a bug report from a customer that the linker was ignoring the
--demangle and --no-demangle options when generating map files.
Moreover, it was failing in a host-dependent way; on Windows hosts,
it was always emitting demangled
We had a bug report from a customer that the linker was ignoring the
--demangle and --no-demangle options when generating map files.
Moreover, it was failing in a host-dependent way; on Windows hosts, it
was always emitting demangled names in the map file, while on Linux
hosts, it never did. M
