public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/46970] [4.3/4.4/4.5/4.6 Regression] wrong code with -Os -ftree-loop-linear
Date: Fri, 17 Dec 2010 17:14:00 -0000	[thread overview]
Message-ID: <bug-46970-4-6R51QluDqO@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-46970-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #5 from Jakub Jelinek <jakub at gcc dot gnu.org> 2010-12-17 17:14:01 UTC ---
Created attachment 22801
  --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=22801
gcc46-pr46970.patch

Untested patch that fixes this and keeps ltrans-3.c working.

I don't feel very good about the +-1 * stepint extra adjustments the code did
and still does though, I'm afraid there could be problems with that if there is
an overflow, but it would be much more work to adjust lambda-code.c so that it
deals with this properly.


  parent reply	other threads:[~2010-12-17 17:14 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-15 20:11 [Bug tree-optimization/46970] New: " zsojka at seznam dot cz
2010-12-16  0:46 ` [Bug tree-optimization/46970] " hjl.tools at gmail dot com
2010-12-16  0:49 ` hjl.tools at gmail dot com
2010-12-16  0:51 ` hjl.tools at gmail dot com
2010-12-16 14:55 ` rguenth at gcc dot gnu.org
2010-12-17 16:17 ` jakub at gcc dot gnu.org
2010-12-17 17:14 ` jakub at gcc dot gnu.org [this message]
2011-01-03 21:01 ` rguenth at gcc dot gnu.org
2011-01-18 20:58 ` spop at gcc dot gnu.org
2011-01-18 20:59 ` spop at gcc dot gnu.org
2011-01-25 21:27 ` spop at gcc dot gnu.org
2011-01-25 21:54 ` spop at gcc dot gnu.org
2011-02-02 17:54 ` dnovillo 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-46970-4-6R51QluDqO@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).