public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "izamyatin at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/53787] New: Possible lto improvement
Date: Wed, 27 Jun 2012 17:26:00 -0000	[thread overview]
Message-ID: <bug-53787-4@http.gcc.gnu.org/bugzilla/> (raw)

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

             Bug #: 53787
           Summary: Possible lto improvement
    Classification: Unclassified
           Product: gcc
           Version: 4.8.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: lto
        AssignedTo: unassigned@gcc.gnu.org
        ReportedBy: izamyatin@gmail.com


For following Fortan test t.f90 icc can propagate loop counter value and then
perform complete unroll and gcc doesn't do it

      real x(10)
      n = 10
      call init(x,n)
      print *, x
      end

      subroutine init(x, n)
      real x(10)
       do i=1,n
         x(i) = i*i + 1
       enddo

       return
       end

 Not sure it's completely lto problem though...

ifort flags    - -O3 -ipo -inline-level=0
gfortran flags - -O3 -flto -fwhole-program -fno-inline


             reply	other threads:[~2012-06-27 17:26 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-27 17:26 izamyatin at gmail dot com [this message]
2012-06-27 17:39 ` [Bug lto/53787] " dominiq at lps dot ens.fr
2012-06-27 17:57 ` izamyatin at gmail dot com
2012-06-27 20:03 ` hjl.tools at gmail dot com
2012-06-28  8:17 ` izamyatin at gmail dot com
2012-06-28  8:22 ` izamyatin at gmail dot com
2012-06-28 10:08 ` [Bug tree-optimization/53787] Possible IPA-SRA / IPA-CP improvement rguenth at gcc dot gnu.org
2012-07-19 19:10 ` izamyatin at gmail dot com
2012-07-20 19:59 ` jamborm at gcc dot gnu.org
2012-07-26 22:49 ` steven at gcc dot gnu.org
2012-07-27  9:35 ` jamborm at gcc dot gnu.org
2012-08-30 15:59 ` jamborm at gcc dot gnu.org
2012-11-07 15:56 ` jamborm at gcc dot gnu.org
2012-11-08 14:43 ` jamborm at gcc dot gnu.org
2013-01-22 15:32 ` ysrumyan at gmail dot com
2013-01-22 15:33 ` ysrumyan at gmail dot com
2013-01-25 18:33 ` jamborm at gcc dot gnu.org
2014-02-14 17:16 ` jamborm at gcc dot gnu.org
2014-02-28 14:26 ` izamyatin at gmail dot com
2014-05-23 15:52 ` jamborm 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-53787-4@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).