public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
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: Thu, 4 May 2023 09:55:34 +0800	[thread overview]
Message-ID: <CAKcpw6XmQ7-PKJZyijoBy-G6shPZ9FNOADVsdX9B9YZcJ4xG8A@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.21.2305022016160.41756@angie.orcam.me.uk>

Maciej W. Rozycki <macro@orcam.me.uk> 于2023年5月3日周三 03:33写道:
>
> On Wed, 26 Apr 2023, YunQiang Su wrote:
>
> > > Since 32f1c80375e "MIPS: support mips*64 as CPU and gnuabi64 as ABI",
> >
> > I will fix the test suite.
> > The reason is that: the previous test suite assumes the default ABI is
> > n32 even the triple
> > with -gnuabi64.
>
>  I can see extra 3346 regressions across various MIPS targets compared to
> a checkout from Jan.  Including ones like (parts of log trimmed for
> clarity):
>
> ../as-new  --defsym count=960 /scratch/vol1/binutils/binutils-mips-test/binutils-src/gas/testsuite/gas/mips/branch-swap-2.s
> gas/testsuite/gas/mips/branch-swap-2.s:1: Fatal error: `micromips' cannot be used with `mips32r6'
> FAIL: MIPS branch swapping (960)
>
> for `mips-img-elf' which indicates that the default architecture has
> changed for GAS for this target.  I think this is due to your commit
> 9171de358f23 ("MIPS: default output r6 obj if the triple is r6"), which
> has this part among others:
>
> +       # 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.

And I am working on fix the tesutsuite for `-gnuabi64` and `mipsisaXXr6`.

>
>   Maciej



-- 
YunQiang Su

  reply	other threads:[~2023-05-04  1:55 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 [this message]
2023-05-07 17:46       ` Maciej W. Rozycki
2023-05-09  3:15         ` YunQiang Su
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=CAKcpw6XmQ7-PKJZyijoBy-G6shPZ9FNOADVsdX9B9YZcJ4xG8A@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).