public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libffi/83636] libffi/mips/n32: don't .set mips4 for mips r6
Date: Mon, 30 Aug 2021 08:05:33 +0000	[thread overview]
Message-ID: <bug-83636-4-WB30ja0Vwx@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-83636-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83636

--- Comment #3 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by YunQiang Su <syq@gcc.gnu.org>:

https://gcc.gnu.org/g:d7e56b084d0b230ae5ee280f569d679fa0f09f4d

commit r12-3219-gd7e56b084d0b230ae5ee280f569d679fa0f09f4d
Author: YunQiang Su <yunqiang.su@cipunited.com>
Date:   Sat Aug 28 08:17:18 2021 -0400

    libffi: Fix MIPS r6 support

    for some instructions, MIPS r6 uses different encoding other than
    the previous releases.

    1. mips/n32.S disable .set mips4: since it casuses old insn encoding
       is used.
       https://github.com/libffi/libffi/pull/396 has been accepted as:
         94c102aa69b04337f63498e0e6551fcdce549ae5
    2. mips/ffi.c: the encoding for JR is hardcoded: we need to use
       different value for r6 and pre-r6.
       https://github.com/libffi/libffi/pull/401 has been accpeted as:
         746dbe3a6a79a41931c03b51df2972be4d5e5028

    libffi/
            PR libffi/83636
            * src/mips/n32.S: disable .set mips4
            * src/mips/ffi.c: use different JR encoding for r6.

  parent reply	other threads:[~2021-08-30  8:05 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-83636-4@http.gcc.gnu.org/bugzilla/>
2021-08-27  5:01 ` syq at debian dot org
2021-08-30  8:05 ` cvs-commit at gcc dot gnu.org [this message]
2023-05-19  6:16 ` syq at debian dot org

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=bug-83636-4-WB30ja0Vwx@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /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).