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/54963] [4.8 Regression] Wrong code generated for libgfortran/generated/eoshift3_8.c on SH
Date: Tue, 30 Oct 2012 01:04:00 -0000	[thread overview]
Message-ID: <bug-54963-4-zMtOb21B5O@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-54963-4@http.gcc.gnu.org/bugzilla/>


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

Oleg Endo <olegendo at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
  Attachment #28551|0                           |1
        is obsolete|                            |

--- Comment #6 from Oleg Endo <olegendo at gcc dot gnu.org> 2012-10-30 01:04:10 UTC ---
Created attachment 28567
  --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=28567
Proposed patch

I'm now testing this patch.  It fixes the overlapping reg negdi problem. 
There's a code size increase in CSiBE:

linux-2.4.23-pre3-testplatform
  lib/vsprintf     4776 -> 4820         +44 / +0.921273 %

I haven't checked the details of this case, but I guess this is the price of
correct code ;)


  parent reply	other threads:[~2012-10-30  1:04 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-17 23:49 [Bug middle-end/54963] New: " kkojima at gcc dot gnu.org
2012-10-20  6:33 ` [Bug target/54963] [4.8 Regression] " kkojima at gcc dot gnu.org
2012-10-20  9:29 ` olegendo at gcc dot gnu.org
2012-10-28 23:01 ` olegendo at gcc dot gnu.org
2012-10-29  0:59 ` kkojima at gcc dot gnu.org
2012-10-29 11:13 ` olegendo at gcc dot gnu.org
2012-10-30  1:04 ` olegendo at gcc dot gnu.org [this message]
2012-10-30  2:46 ` kkojima at gcc dot gnu.org
2012-10-30  9:23 ` olegendo at gcc dot gnu.org
2012-11-01  0:01 ` olegendo at gcc dot gnu.org
2012-11-01  0:13 ` kkojima 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-54963-4-zMtOb21B5O@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).