This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: Fix for PR70481 Libiberty Demangler

From: Jeff Law <law at redhat dot com>
To: Bernd Schmidt <bschmidt at redhat dot com>, Marcel BÃhme <boehme dot marcel at gmail dot com>, gcc-patches at gcc dot gnu dot org
Date: Thu, 31 Mar 2016 11:33:11 -0600
Subject: Re: Fix for PR70481 Libiberty Demangler
Authentication-results: sourceware.org; auth=none
References: <FFF82524-71F3-4227-A4DB-C9D7779663F5 at gmail dot com> <56FD5CCB dot 5000002 at redhat dot com> <56FD5E77 dot 1050100 at redhat dot com>

On 03/31/2016 11:29 AM, Bernd Schmidt wrote:

On 03/31/2016 07:22 PM, Jeff Law wrote:

@@ -1237,11 +1237,13 @@  squangle_mop_up (struct work_stuff *work)

Thanks.  I've just installed this patch, along with suitable tests from
70481 and 67394.


What are the rules for modifying libiberty again? Do we have to patch
binutils/gdb at the same time, or is there an automated process?

My recollection is that gcc is considered the master for libiberty andthe gdb project will resync as needed.


jeff

References:
- Fix for PR70481 Libiberty Demangler
  - From: Marcel BÃhme
- Re: Fix for PR70481 Libiberty Demangler
  - From: Jeff Law
- Re: Fix for PR70481 Libiberty Demangler
  - From: Bernd Schmidt

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]