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 ada/98996] [11 Regression] mips64 ada ftbfs Date: Fri, 26 Feb 2021 02:56:19 +0000 [thread overview] Message-ID: <bug-98996-4-nlk3TT2B4X@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-98996-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98996 --- Comment #4 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Jeff Law <law@gcc.gnu.org>: https://gcc.gnu.org/g:9967bbfceddce755b18bdbecc6d0c56e994a05cc commit r11-7413-g9967bbfceddce755b18bdbecc6d0c56e994a05cc Author: YunQiang Su <yunqiang.su@cipunited.com> Date: Thu Feb 25 19:55:10 2021 -0700 [PATCH v4 1/2] MIPS: unaligned load: use SImode for SUBREG if OK (PR98996) [PATCH v4 2/2] ada: add 128bit operation for MIPS N32 and N64 gcc/ChangeLog: PR target/98996 * config/mips/mips.c (mips_expand_ext_as_unaligned_load): If TARGET_64BIT and dest is SUBREG, we check the width, if it equal to SImode, we use SImode operation, just like what we are doing for REG one. gcc/ada/ChangeLog: PR ada/98996 * Makefile.rtl: <mips*-*-linux*> add 128Bit operation file for MIPS N64 and N32 to LIBGNAT_TARGET_PAIRS and EXTRA_GNATRTL_NONTASKING_OBJS
next prev parent reply other threads:[~2021-02-26 2:56 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-02-08 2:42 [Bug ada/98996] New: " syq at debian dot org 2021-02-13 13:03 ` [Bug ada/98996] " syq at debian dot org 2021-02-14 0:32 ` syq at debian dot org 2021-02-16 8:18 ` [Bug ada/98996] [11 Regression] " doko at gcc dot gnu.org 2021-02-23 12:06 ` rguenth at gcc dot gnu.org 2021-02-26 2:56 ` cvs-commit at gcc dot gnu.org [this message] 2021-02-26 12:53 ` rguenth at gcc dot gnu.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-98996-4-nlk3TT2B4X@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: linkBe 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).