public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Richard Earnshaw <Richard.Earnshaw@foss.arm.com>
To: Frederic Cambus <fred@statdns.com>, binutils@sourceware.org
Subject: Re: [PATCH] Add OpenBSD ARM Little Endian BFD support.
Date: Tue, 30 Aug 2022 14:55:00 +0100	[thread overview]
Message-ID: <12d112cf-923c-81f7-0580-a1e5c33474f5@foss.arm.com> (raw)
In-Reply-To: <YwpUPig8HbI0dxxE@Freds-MacBook-Air.local>



On 27/08/2022 18:28, Frederic Cambus wrote:
> bfd/ChangeLog:
> 
> 2022-08-27  Frederic Cambus  <fred@statdns.com>
> 
> 	* config.bfd (arm-*-openbsd*): Add target.
> ---
>   bfd/config.bfd | 5 ++++-
>   1 file changed, 4 insertions(+), 1 deletion(-)
> 
> diff --git a/bfd/config.bfd b/bfd/config.bfd
> index 8c7be5da38a..0a47bf0484c 100644
> --- a/bfd/config.bfd
> +++ b/bfd/config.bfd
> @@ -90,7 +90,6 @@ case $targ in
>    arm*-*-aout | \
>    arm-*-coff | \
>    arm*-*-netbsdaout* | \
> - arm-*-openbsd* | \
>    arm-*-oabi | \
>    arm-*-riscix* | \
>    arm*-*-symbianelf* | \
> @@ -387,6 +386,10 @@ case "${targ}" in
>       targ_defvec=arm_elf32_le_vec
>       targ_selvecs="arm_elf32_be_vec"
>       ;;
> +  arm-*-openbsd*)
> +    targ_defvec=arm_elf32_le_vec
> +    targ_selvecs="arm_elf32_be_vec"
> +    ;;
>     arm-*-nto* | nto*arm*)
>       targ_defvec=arm_elf32_le_vec
>       targ_selvecs=arm_elf32_be_vec
> 

This is exactly the same content as the entry directly above it 
(netbsd), so please merge the two.  It's a maintenance burden to have a 
lot of duplicated entries.

R.

  reply	other threads:[~2022-08-30 13:55 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-27 17:28 Frederic Cambus
2022-08-30 13:55 ` Richard Earnshaw [this message]
2022-08-31 22:12   ` Frederic Cambus
2022-09-01  9:43     ` Richard Earnshaw
2022-09-01 15:56       ` Frederic Cambus
2022-09-02 10:31         ` Nick Clifton

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=12d112cf-923c-81f7-0580-a1e5c33474f5@foss.arm.com \
    --to=richard.earnshaw@foss.arm.com \
    --cc=binutils@sourceware.org \
    --cc=fred@statdns.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).