From: Andrew Burgess <aburgess@redhat.com>
To: gdb-patches@sourceware.org, binutils@sourceware.org
Subject: Re: [PATCH] libiberty: sync with gcc commit df3510f80e7c02d9
Date: Sat, 20 Jun 2026 13:54:57 +0100 [thread overview]
Message-ID: <875x3dpe1q.fsf@redhat.com> (raw)
In-Reply-To: <ff87d7cb74f9d3d3b81aeca0a979d3dcc1531567.1781002240.git.aburgess@redhat.com>
Andrew Burgess <aburgess@redhat.com> writes:
> Sync the libiberty/ directory with gcc commit
> df3510f80e7c02d9c19d7cb33759cd925880f53a. This pulls in the following
> gcc commits and the associated updates to 'libiberty/ChangeLog':
>
> * 06fb00cb66d libiberty: Fix typos in various files
> * fbf903e5b9f Re-flow lines made longer than 80 characters by typo fixes
> * cfb945957ee Regenerate some autoconf configure scripts after recent spelling fixes.
> * bc4d9b6aeb3 libiberty: avoid exponential back reference issue in D demangler
>
> I have retained the changes that are in the following binutils-gdb
> commit, which are not in gcc:
>
> commit 219822fd5db6305592b45677a3b38c02b523360e
> Date: Tue Apr 9 06:39:21 2024 -0700
>
> mmap: Avoid the sanitizer configure check failure
I've gone ahead and checked this in. If there are any problems then
just let me know.
Thanks,
Andrew
prev parent reply other threads:[~2026-06-20 12:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-09 10:52 Andrew Burgess
2026-06-09 11:13 ` Andrew Burgess
2026-06-20 12:54 ` Andrew Burgess [this message]
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=875x3dpe1q.fsf@redhat.com \
--to=aburgess@redhat.com \
--cc=binutils@sourceware.org \
--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