From: YunQiang Su <wzssyqa@gmail.com>
To: "Maciej W. Rozycki" <macro@orcam.me.uk>
Cc: Alan Modra <amodra@gmail.com>,
binutils@sourceware.org, YunQiang Su <yunqiang.su@cipunited.com>,
RichardSandifordrichard.sandiford@arm.com,
Chenghua Xu <paul.hua.gm@gmail.com>
Subject: Re: mips64-linux-gnuabi64 testsuite breakage
Date: Tue, 9 May 2023 11:15:28 +0800 [thread overview]
Message-ID: <CAKcpw6Xmw1f7g1f4+edAEKzMByfcmpFkBF4gLyJ9ePJ-brTaDw@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.21.2305071836490.54316@angie.orcam.me.uk>
Maciej W. Rozycki <macro@orcam.me.uk> 于2023年5月8日周一 01:46写道:
>
> On Thu, 4 May 2023, YunQiang Su wrote:
>
> > > + # If Vendor is IMG, then MIPSr6 is used
> > > + case ${target} in
> > > + mips*64*-img-*)
> > > + mips_cpu=mips64r6
> > > + ;;
> > > + mips*-img-*)
> > > + mips_cpu=mips32r6
> > > + ;;
> > > + esac
> > >
> > > Not only this change is wrong (you can't just arbitrarily change a
> > > configuration that has been in the wild for ~8.5 years as it'll break
> > > things for people who rely on the established semantics), but it hasn't
> > > been properly verified either, as a change is supposed not to cause
> > > regressions in the testsuite.
> > >
> > > Please revert the part quoted and fix the regressions. Thank you.
> >
> > Reverted.
>
> Thank you.
>
> FAOD if you think a triplet that implicitly defaults to R6 is useful,
No, I don't think that it is useful at all. It is so uglyyyyyyy.
In fact, we should use the correct cpu name in triple, just like
mipsisa32r6 etc.
> then feel free to submit a change for say `mips*-cipunited-*' to do so (or
> maybe `mips*-cip-*' if you want to keep it short and the company policy
> allows using such a short name), as this would be a configuration that had
> no previous mention/semantics in our tree and therefore I would have no
> concerns about it.
>
No, I won't. I submit the patch about `img`, is due to that, this vendor value
did/does/being used.
IMG/MIPS/Wave/MIPS does provide the toolchain with img as its vendor name,
and the default arch is R6.
https://codescape.mips.com/components/toolchain/2021.09-01/downloads.html
> Overall I'd suggest the `--with-arch=' approach previously discussed and
> already implemented for MIPS targets in GCC and also some other targets in
> binutils. It is more generic, although it may complicate testing, so it
> may have to be deployed with care.
>
> > And I am working on fix the tesutsuite for `-gnuabi64` and `mipsisaXXr6`.
>
> I look forward to your fixes.
>
> Maciej
--
YunQiang Su
next prev parent reply other threads:[~2023-05-09 3:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-26 4:53 Alan Modra
2023-04-26 5:46 ` YunQiang Su
2023-05-02 19:33 ` Maciej W. Rozycki
2023-05-04 1:55 ` YunQiang Su
2023-05-07 17:46 ` Maciej W. Rozycki
2023-05-09 3:15 ` YunQiang Su [this message]
2023-05-09 8:13 ` Richard Sandiford
2023-05-18 15:58 ` Maciej W. Rozycki
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=CAKcpw6Xmw1f7g1f4+edAEKzMByfcmpFkBF4gLyJ9ePJ-brTaDw@mail.gmail.com \
--to=wzssyqa@gmail.com \
--cc=RichardSandifordrichard.sandiford@arm.com \
--cc=amodra@gmail.com \
--cc=binutils@sourceware.org \
--cc=macro@orcam.me.uk \
--cc=paul.hua.gm@gmail.com \
--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).