public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Sergei Organov <osv@topconrd.ru>
To: Andrew Pinski <pinskia@physics.uc.edu>
Cc: gcc@gcc.gnu.org
Subject: Re: How to replace -O1 with corresponding -f's?
Date: Mon, 20 Jun 2005 14:55:00 -0000	[thread overview]
Message-ID: <87zmtl84eo.fsf@osv.topcon.com> (raw)
In-Reply-To: <44a7432710d6ca83042f60c9fbab58d9@physics.uc.edu>

Andrew Pinski <pinskia@physics.uc.edu> writes:

> On Jun 20, 2005, at 10:04 AM, Andrew Haley wrote:
> >> How one finds out what optimization pass misbehaves?
> >
> > Look at the dumps.  If you use the gcc option -da you'll get a full
> > set of RTL dump files.
>
> And -fdump-tree-all for the tree dumps.

The last const.c.t69.final_cleanup is exactly the same in both cases and
doesn't have any useful information anyway:


;; Function osvf (osvf)

osvf ()
{
<bb 0>:
  return 3.14314314e+8;

}

In fact, at the RTL level the difference is that non-optimized code


(insn 8 6 9 1 (set (reg:DF 118 [ D.1144 ])
        (mem/u/i:DF (symbol_ref:SI ("osv") [flags 0x6] <var_decl 0x401ab32c osv>
    (nil))

(insn 9 8 10 1 (set (reg:DF 119 [ <result> ])
        (reg:DF 118 [ D.1144 ])) -1 (nil)
    (nil))

gets replaced with "optimized" one:

(insn 10 9 11 1 (set (reg:SI 121)
        (high:SI (symbol_ref/u:SI ("*.LC0") [flags 0x2]))) -1 (nil)
    (nil))

(insn 11 10 12 1 (set (reg/f:SI 120)
        (lo_sum:SI (reg:SI 121)
            (symbol_ref/u:SI ("*.LC0") [flags 0x2]))) -1 (nil)
    (expr_list:REG_EQUAL (symbol_ref/u:SI ("*.LC0") [flags 0x2])
        (nil)))

(insn 12 11 13 1 (set (reg:DF 118 [ <result> ])
        (mem/u/i:DF (reg/f:SI 120) [0 S8 A64])) -1 (nil)
    (expr_list:REG_EQUAL (const_double:DF 3.14314314e+8 [0x0.95e0725p+29])
        (nil)))

so SYMBOL_FLAG_SMALL (flags 0x6 vs 0x2) is somehow being missed when -O1
is turned on. Seems to be something at tree-to-RTX conversion time.
Constant folding?

-- 
Sergei.

  reply	other threads:[~2005-06-20 14:55 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-20 13:40 Sergei Organov
2005-06-20 14:04 ` Andrew Haley
2005-06-20 14:26   ` Andrew Pinski
2005-06-20 14:55     ` Sergei Organov [this message]
2005-06-20 15:01       ` Andrew Pinski
2005-06-20 15:29         ` Sergei Organov
2005-06-20 15:36           ` Andrew Pinski
2005-06-20 15:58             ` Sergei Organov
2005-06-21  9:55               ` Michael Meissner
2005-06-21 12:49                 ` Sergei Organov
2005-06-20 17:18             ` Sergei Organov
2005-06-24 16:09             ` Sergei Organov
2005-06-20 14:28   ` Sergei Organov
2005-06-22 19:29     ` Zack Weinberg
2005-06-20 14:25 ` Scott Robert Ladd
2005-06-20 14:35 ` Andrew Pinski
2005-06-20 15:04   ` Sergei Organov

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=87zmtl84eo.fsf@osv.topcon.com \
    --to=osv@topconrd.ru \
    --cc=gcc@gcc.gnu.org \
    --cc=pinskia@physics.uc.edu \
    /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).