From: YunQiang Su <wzssyqa@gmail.com>
To: Nick Clifton <nickc@redhat.com>, YunQiang Su <yunqiang.su@cipunited.com>
Cc: binutils@sourceware.org
Subject: Re: [PATCH v4] MIPS: Use 64-bit a ABI by default for `mipsisa64*-*-linux*' targets
Date: Tue, 2 Jan 2024 17:30:23 +0800 [thread overview]
Message-ID: <CAKcpw6U6UNQZJ+cj8i49cxFNaE6Mg2L6b8Fosjobkc7kJ4PGoQ@mail.gmail.com> (raw)
In-Reply-To: <1a67ce3e-f050-4ac4-aa81-50eb746160a0@gmail.com>
YunQiang Su <wzssyqa@gmail.com> 于2023年12月1日周五 08:56写道:
>
>
>
> 在 2023/11/30 21:40, Nick Clifton 写道:
> > Hi YunQiang Su,
> >
> >>> Following the arrangement in GCC select a 64-bit ABI by default, either
> >>> n32 or n64, rather than o32 for `mipsisa64*-*-linux*' targets, just as
> >>> with the corresponding `mips64*-*-linux*' targets.
> >>> ---
> >>
> >> ping
> >
> > Sorry - I meant to post that I am leaving this one to Maciej. I am
> > concerned
> > that changing the target matching for those targets might affect already
> > existing users who are expecting the old behaviour. I do not know if
> > this is
> > possible/likely however, so I would prefer to leave the decision to someone
> > who has much more knowledge of the MIPS target than myself, ie Maciej.
> >
>
> https://sourceware.org/pipermail/binutils/2023-August/128758.html
> In this post, Maciej suggested that we can limit mips*64-* to
> mipsisa64*-linux*.
>
ping.
This config has been in gcc since 2008, with this commit:
f2d6ca5081ba8fb31b5d03545f45cce12ac67b3f
> > Cheers
> > Nick
> >
--
YunQiang Su
prev parent reply other threads:[~2024-01-02 9:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-17 9:03 YunQiang Su
2023-11-29 6:13 ` YunQiang Su
2023-11-30 13:40 ` Nick Clifton
2023-12-01 0:56 ` YunQiang Su
2024-01-02 9:30 ` YunQiang Su [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=CAKcpw6U6UNQZJ+cj8i49cxFNaE6Mg2L6b8Fosjobkc7kJ4PGoQ@mail.gmail.com \
--to=wzssyqa@gmail.com \
--cc=binutils@sourceware.org \
--cc=nickc@redhat.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).