public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "olegendo at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/49468] SH Target: inefficient integer abs code
Date: Tue, 28 Feb 2012 08:44:00 -0000	[thread overview]
Message-ID: <bug-49468-4-OiR04iWnTj@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-49468-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #8 from Oleg Endo <olegendo at gcc dot gnu.org> 2012-02-28 08:41:28 UTC ---
Created attachment 26768
  --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=26768
Patch to add DImode abs

The attached patch adds DImode abs and did not introduce new failures when
tested against rev 184589.
I'm a bit confused, as this is exactly the same code as I used before to add
DImode abs, and before it was failing in some cases.  Either there was another
bug that got fixed in the middle-end optimizers, or this is just coincidence. 
I've seen that other expanders use force_reg to make sure that operands will be
in regs ... would that be the safer way of doing it?


  parent reply	other threads:[~2012-02-28  8:42 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-19 15:15 [Bug target/49468] New: " oleg.endo@t-online.de
2011-06-19 15:30 ` [Bug target/49468] " oleg.endo@t-online.de
2011-06-19 15:49 ` oleg.endo@t-online.de
2011-06-22 22:38 ` kkojima at gcc dot gnu.org
2011-06-26 20:49 ` oleg.endo@t-online.de
2011-06-27  6:40 ` kkojima at gcc dot gnu.org
2011-06-29  1:37 ` oleg.endo@t-online.de
2011-09-25 12:53 ` oleg.endo@t-online.de
2012-02-26 23:38 ` olegendo at gcc dot gnu.org
2012-02-28  8:44 ` olegendo at gcc dot gnu.org [this message]
2012-02-29 23:23 ` kkojima at gcc dot gnu.org
2012-03-14 23:10 ` olegendo at gcc dot gnu.org
2013-12-05 19:26 ` olegendo 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-49468-4-OiR04iWnTj@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).