From: Sam James <sam@gentoo.org>
To: Tom Tromey <tom@tromey.com>
Cc: binutils@sourceware.org, gdb-patches@sourceware.org
Subject: Re: [PATCH] libiberty: sync with gcc
Date: Fri, 22 Nov 2024 15:46:39 +0000 [thread overview]
Message-ID: <87iksfb7a8.fsf@gentoo.org> (raw)
In-Reply-To: <87cyinthe8.fsf@tromey.com> (Tom Tromey's message of "Fri, 22 Nov 2024 08:30:55 -0700")
Tom Tromey <tom@tromey.com> writes:
>>>>>> "Sam" == Sam James <sam@gentoo.org> writes:
>
> Sam> This imports the following commits from GCC as of r15-5375-gbeec291225be9b:
> Sam> 94bea5dd6c9a libiberity: ANSIfy test-demangle.c
> Sam> aa84020b2edb libiberty: Fix comment typos
> Sam> c1b2100e736c libiberty: Restore build with CP_DEMANGLE_DEBUG defined
> Sam> bb8dd0980b39 libiberty: Fix up > 64K section handling in simple_object_elf_copy_lto_debug_section [PR116614]
> Sam> ---
> Sam> OK? This primarily fixes a C23 issue in test-demangle.c.
>
> Thank you. Please check this in.
> Approved-By: Tom Tromey <tom@tromey.com>
Thanks. I'm going to add this commit on top to catch another change
which went in later:
diff --git a/libiberty/ChangeLog b/libiberty/ChangeLog
index 4a461602ac0..83e9120c444 100644
--- a/libiberty/ChangeLog
+++ b/libiberty/ChangeLog
@@ -1,3 +1,7 @@
+2024-11-19 Evgeny Karpov <evgeny.karpov@microsoft.com>
+
+ * simple-object-coff.c: Add aarch64.
+
2024-11-16 Andrew Pinski <quic_apinski@quicinc.com>
* testsuite/test-demangle.c (get_line): Change K&R style
diff --git a/libiberty/simple-object-coff.c b/libiberty/simple-object-coff.c
index e748205972f..fd3c310db51 100644
--- a/libiberty/simple-object-coff.c
+++ b/libiberty/simple-object-coff.c
@@ -219,7 +219,9 @@ static const struct coff_magic_struct coff_magic[] =
/* i386. */
{ 0x14c, 0, F_EXEC | IMAGE_FILE_SYSTEM | IMAGE_FILE_DLL },
/* x86_64. */
- { 0x8664, 0, F_EXEC | IMAGE_FILE_SYSTEM | IMAGE_FILE_DLL }
+ { 0x8664, 0, F_EXEC | IMAGE_FILE_SYSTEM | IMAGE_FILE_DLL },
+ /* AArch64. */
+ { 0xaa64, 0, F_EXEC | IMAGE_FILE_SYSTEM | IMAGE_FILE_DLL }
};
/* See if we have a COFF file. */
>
> Tom
thanks,
sam
next prev parent reply other threads:[~2024-11-22 15:47 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-18 6:02 Sam James
2024-11-22 15:30 ` Tom Tromey
2024-11-22 15:46 ` Sam James [this message]
2024-11-22 23:43 ` Tom Tromey
-- strict thread matches above, loose matches on Subject: below --
2025-07-10 13:30 Matthieu Longo
2025-07-23 17:36 ` Tom Tromey
2025-07-25 9:17 ` Matthieu Longo
2025-05-14 11:49 Andreas Schwab
2024-08-20 17:01 Andrew Burgess
2024-09-04 16:07 ` Andrew Burgess
2024-06-29 17:17 Sam James
2024-07-12 7:55 ` Sam James
2024-07-12 8:06 ` Nick Clifton
2024-07-12 21:49 ` Sam James
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=87iksfb7a8.fsf@gentoo.org \
--to=sam@gentoo.org \
--cc=binutils@sourceware.org \
--cc=gdb-patches@sourceware.org \
--cc=tom@tromey.com \
/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