Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <palves@redhat.com>
To: GDB Patches <gdb-patches@sourceware.org>
Cc: Joel Brobecker <brobecker@adacore.com>
Subject: FYI, Pushed 5 demangler patches to 7.10 branch
Date: Sat, 28 Nov 2015 17:34:00 -0000	[thread overview]
Message-ID: <5659E5B4.6000107@redhat.com> (raw)

Hi all,

FYI, I've merged the below demangler changes/fixes to the 7.10 branch.

I've mainly wanted the "PR other/61321" fix below, which is really
GDB PR 16957 and probably others.  But, I thought it better to
just merge all demangler fixes we have in master -- it was both
easier, and I think safer this way, and of course fewer crashes/bugs
should be nicer for users.  :-)

I'll update the release wiki page as soon as I have a chance.

Ian Lance Taylor (1):
  Demangler: Fix constructor names with ABI tags

Jason Merrill (1):
  Implement N4514, C++ Extensions for Transactional Memory.

Mikhail Maltsev (1):
  Fix several crashes of C++ demangler on fuzzed input.

Pedro Alves (2):
  PR other/61321 - demangler crash on casts in template parameters
  Adjust GDB to demangler API change

 gdb/ChangeLog                         |   5 ++
 libiberty/ChangeLog                   |  51 ++++++++++++++++
 gdb/cp-name-parser.y                  |   2 +-
 include/demangle.h                    |   6 ++
 libiberty/cp-demangle.c               | 111 ++++++++++++++++++++++++++++------
 libiberty/cp-demangle.h               |  29 ++++++++-
 libiberty/cp-demint.c                 |   1 +
 libiberty/testsuite/demangle-expected |  62 +++++++++++++++++++
 8 files changed, 245 insertions(+), 22 deletions(-)

-- 
1.9.3


             reply	other threads:[~2015-11-28 17:34 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-28 17:34 Pedro Alves [this message]
2015-11-30 12:22 ` Pedro Alves
2015-12-04 10:36   ` Joel Brobecker

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5659E5B4.6000107@redhat.com \
    --to=palves@redhat.com \
    --cc=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox