public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "matthew.fortune at imgtec dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/51729] dspr2-MULT.c and dspr2-MULTU.c fail for MIPS
Date: Thu, 31 Jul 2014 15:19:00 -0000 [thread overview]
Message-ID: <bug-51729-4-CAaWHa2T8P@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-51729-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=51729
Matthew Fortune <matthew.fortune at imgtec dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |clm at codesourcery dot com,
| |matthew.fortune at imgtec dot com,
| |sandra at codesourcery dot com
--- Comment #3 from Matthew Fortune <matthew.fortune at imgtec dot com> ---
The affected tests appear to have started passing again since this commit:
svn: r211959
2014-06-24 Catherine Moore <clm@codesourcery.com>
Sandra Loosemore <sandra@codesourcery.com>
gcc/
* config/mips/mips.c (mips_order_regs_for_local_alloc): Delete.
* config/mips/mips.h (ADJUST_REG_ALLOC_ORDER): Delete.
* config/mips/mips-protos.h (mips_order_regs_for_local_alloc): Delete.
Irritatingly they now pass for -O2 and -O3 but still fail for -O1 and -Os. I
was half tempted to submit a patch to just be content that we get multiple
accumulators now used at -O2 and -O3 and leave it at that but I think that is
probably the wrong attitude.
Has anyone else noticed the change in state for these tests and looked into it,
planning to look into it or have any thoughts? I'll take a look when I get
chance.
prev parent reply other threads:[~2014-07-31 15:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-02 11:26 [Bug target/51729] New: " rsandifo at gcc dot gnu.org
2012-01-02 11:34 ` [Bug target/51729] " rsandifo at gcc dot gnu.org
2012-01-04 1:20 ` pinskia at gcc dot gnu.org
2014-07-31 15:19 ` matthew.fortune at imgtec dot com [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=bug-51729-4-CAaWHa2T8P@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).