public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "meissner at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/63501] ICE in GCC powerpc64le top of trunk with -mupper-regs-df
Date: Fri, 10 Oct 2014 17:03:00 -0000	[thread overview]
Message-ID: <bug-63501-4-7e1WDVvEV3@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-63501-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #3 from Michael Meissner <meissner at gcc dot gnu.org> ---
The -mupper-regs-df and -mupper-regs-sf options are a work in progress.  I am
working on these options right now on a private branch, but the code is not yet
ready for incorporation into the tree.  I don't know how long it will take to
track down the various bugs before the patches are submitted.

As I write this, the code in my branch requires the use of the -mlra option (to
switch to the LRA register allocator), and -mlra has some issues of its own
that we are investigating.

I have two spec tests (456.hmmer and 416.gamess) that fail when the
-mupper-regs-df -mlra options are used.  Of the tests that run, 454.calculix
and 470.lbm show about a 6-7% improvement, while 410.bwaves has a 6-7%
regression.


  parent reply	other threads:[~2014-10-10 17:03 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-09 18:09 [Bug target/63501] New: " saugustine at google dot com
2014-10-09 18:18 ` [Bug target/63501] " dje at gcc dot gnu.org
2014-10-09 18:20 ` dje at gcc dot gnu.org
2014-10-09 18:21 ` dje at gcc dot gnu.org
2014-10-10 17:03 ` meissner at gcc dot gnu.org [this message]
2014-10-10 18:44 ` bergner at gcc dot gnu.org
2015-02-17 18:01 ` bergner 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-63501-4-7e1WDVvEV3@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).