public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ramana at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/57462] ira-costs considers only a single register at a time
Date: Wed, 10 Jul 2013 22:10:00 -0000	[thread overview]
Message-ID: <bug-57462-4-I3uvDFkQwi@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-57462-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57462

Ramana Radhakrishnan <ramana at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |ramana at gcc dot gnu.org

--- Comment #3 from Ramana Radhakrishnan <ramana at gcc dot gnu.org> ---
This is part of the reason why on trunk we currently disable 64 bit arithmetic
in neon in a large number of cases. It's sometimes just not worth it -
Additionally neon doesn't have comparison operations so many times one has
noticed that we keep doing a lot of operations on the neon side and then you
just have to move back to the integer side to the comparisons. So there are
times when this doesn't happen properly. 

Ramana


  parent reply	other threads:[~2013-07-10 22:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-57462-4@http.gcc.gnu.org/bugzilla/>
2013-05-31 13:55 ` vmakarov at redhat dot com
2013-06-03 21:18 ` josh.m.conner at gmail dot com
2013-07-10 22:10 ` ramana at gcc dot gnu.org [this message]
2015-01-23 10:32 ` ramana 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-57462-4-I3uvDFkQwi@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).