public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Richard Sandiford <richard.sandiford@arm.com>
To: YunQiang Su <syq@debian.org>
Cc: "Maciej W. Rozycki" <macro@orcam.me.uk>,
	 Jiaxun Yang <jiaxun.yang@flygoat.com>,
	 YunQiang Su <yunqiang.su@cipunited.com>,
	 Binutils <binutils@sourceware.org>,
	 Xi Ruoyao <xry111@xry111.site>
Subject: Re: [PATCH] MIPS: gas: alter 64 or 32 for r6 triples if march is implicit
Date: Tue, 09 May 2023 08:58:23 +0100	[thread overview]
Message-ID: <mpty1lyq6lc.fsf@arm.com> (raw)
In-Reply-To: <CAKcpw6UsLHasFC7G5a_Pfh1VBfoTbfP4sDqGCNpca8Q5k6jyHA@mail.gmail.com> (YunQiang Su's message of "Tue, 9 May 2023 11:16:10 +0800")

YunQiang Su <syq@debian.org> writes:
> Let's be back to the problem of this patch: what should we do for
>      mipsisa32rXel-*-as -64
> and
>     mipsisa64rXel-*-as -32
> We have several options:
> 1. Keep current, aka issue an error message and exit for 32-64 combination.
> 2. set the default arch to mips64r6 only for mipsisa32r6, aka not for
> mipsisa32r[1-5].
>     set the default arch to mips32r6 only for mipsisa64r6, aka not for
> mipsisa32r[1-5].
>     That's what I did in this patch.
> 3. set the default arch to mips64rN for mipsisa32rN
>     set the default arch to mips32rN for mipsisa64rN
>     but do nothing for any other triples, such as
>        mipstx39* or mips64vr,
>     Since it's hard to determine which arches are best for them.

Personally, I think we should do this one, similarly to your
9171de358f230b64646bbb525a74e5f8e3dbe0dc.  IMO it's better to think
of mipsr6+ as a separate ISA group from pre-r6, since no pair of ISAs
from either group is binary compatible in either direction.

So for mipsr6+ toolchains (those with a mipsr6+ triplet), from-abi
should select the appropriate r6 ISA rather than mips1 or mips3.

Thanks,
Richard

> 4. Set the default 32/64 arch for all triples.

  reply	other threads:[~2023-05-09  7:58 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-06  8:37 YunQiang Su
2023-05-06  8:42 ` Jiaxun Yang
2023-05-06  8:52   ` YunQiang Su
2023-05-06  9:15     ` Jiaxun Yang
2023-05-07 18:17       ` Maciej W. Rozycki
2023-05-07 18:34         ` Jiaxun Yang
2023-05-07 19:01           ` Maciej W. Rozycki
2023-05-08  9:16             ` YunQiang Su
2023-05-08 12:25               ` Maciej W. Rozycki
2023-05-08 13:00                 ` YunQiang Su
2023-05-08 14:43                   ` Maciej W. Rozycki
2023-05-08 19:06                     ` Maciej W. Rozycki
2023-05-09  3:16                       ` YunQiang Su
2023-05-09  7:58                         ` Richard Sandiford [this message]
2023-05-08  9:18           ` YunQiang Su
2023-05-08  9:39           ` Andreas Schwab
2023-05-08 10:51             ` YunQiang Su

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=mpty1lyq6lc.fsf@arm.com \
    --to=richard.sandiford@arm.com \
    --cc=binutils@sourceware.org \
    --cc=jiaxun.yang@flygoat.com \
    --cc=macro@orcam.me.uk \
    --cc=syq@debian.org \
    --cc=xry111@xry111.site \
    --cc=yunqiang.su@cipunited.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).