From: Nick Clifton <nickc@redhat.com>
To: Christophe Lyon <christophe.lyon@linaro.org>,
binutils@sourceware.org, richard.earnshaw@arm.com
Subject: Re: [PATCH] arm: Make 'conflicting CPU architectures' error message more user-friendly
Date: Mon, 4 Sep 2023 13:19:09 +0100 [thread overview]
Message-ID: <21813bc7-2b06-e0fe-0f02-5d12e190d40b@redhat.com> (raw)
In-Reply-To: <20230901135958.186407-1-christophe.lyon@linaro.org>
Hi Christophe,
> Error messages such as "conflicting CPU architectures 10/16" are not
> very to understand, so this patch replaces the numbers with the
> description they actually mean:
> "conflicting CPU architectures ARM v7E-M vs Pre v4"
>
> 2023-09-01 Christophe Lyon <christophe.lyon@linaro.org>
>
> bfd/
> * elf32-arm.c (tag_cpu_arch_combine): Add name_table parameter and
> use it.
> (elf32_arm_merge_eabi_attributes): Update call to
> tag_cpu_arch_combine.
>
> ld/
> * testsuite/ld-arm/attr-merge-9.out: Update expected error
> message.
> * testsuite/ld-arm/attr-merge-arch-2.d: Likewise.
>
Approved - please apply.
Cheers
Nick
prev parent reply other threads:[~2023-09-04 12:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-01 13:59 Christophe Lyon
2023-09-04 12:19 ` Nick Clifton [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=21813bc7-2b06-e0fe-0f02-5d12e190d40b@redhat.com \
--to=nickc@redhat.com \
--cc=binutils@sourceware.org \
--cc=christophe.lyon@linaro.org \
--cc=richard.earnshaw@arm.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).