Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Nick Clifton <nickc@redhat.com>
To: Sam James <sam@gentoo.org>, binutils@sourceware.org
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] libiberty: sync with gcc
Date: Fri, 12 Jul 2024 09:06:15 +0100	[thread overview]
Message-ID: <db5e6d20-2287-4dae-8be7-e8481843f8ad@redhat.com> (raw)
In-Reply-To: <87bk339h92.fsf@gentoo.org>

Hi Sam,

> Sam James <sam@gentoo.org> writes:
> 
>> This imports the following commits from GCC as of r15-1722-g7682d115402743:
>> 	ca2f7c84927f libiberty: Invoke D demangler when --format=auto
>> 	94792057ad4a Fix up duplicated words mostly in comments, part 1
>> 	20e57660e64e libiberty: Fix error return value in pex_unix_exec_child [PR113957].
>> 	52ac4c6be866 [libiberty] remove TBAA violation in iterative_hash, improve code-gen
>> 	53bb7145135c libiberty: Fix up libiberty_vprintf_buffer_size
>> 	65388b28656d c++, demangle: Implement https://github.com/itanium-cxx-abi/cxx-abi/issues/148 non-proposal
>> ---
> 
> ping. It might be nice for this to get in for binutils-2.43 branching
> given the UB fix for hashing.

Yes you are right - please commit as soon as you can! :-)

Thanks for the reminder.

Cheers
   Nick


  reply	other threads:[~2024-07-12  8:06 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-29 17:17 Sam James
2024-07-12  7:55 ` Sam James
2024-07-12  8:06   ` Nick Clifton [this message]
2024-07-12 21:49     ` Sam James
2024-08-20 17:01 Andrew Burgess
2024-09-04 16:07 ` Andrew Burgess
2024-11-18  6:02 Sam James
2024-11-22 15:30 ` Tom Tromey
2024-11-22 15:46   ` Sam James
2024-11-22 23:43     ` Tom Tromey
2025-05-14 11:49 Andreas Schwab
2025-07-10 13:30 Matthieu Longo
2025-07-23 17:36 ` Tom Tromey
2025-07-25  9:17   ` Matthieu Longo

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=db5e6d20-2287-4dae-8be7-e8481843f8ad@redhat.com \
    --to=nickc@redhat.com \
    --cc=binutils@sourceware.org \
    --cc=gdb-patches@sourceware.org \
    --cc=sam@gentoo.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