public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/51506] Function cloning misses constant struct at -Os vs -O2
Date: Mon, 19 Jul 2021 03:06:54 +0000	[thread overview]
Message-ID: <bug-51506-4-xwgHH88FiA@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-51506-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=51506

Andrew Pinski <pinskia at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
          Component|tree-optimization           |ipa
            Summary|Function cloning misses     |Function cloning misses
                   |constant struct             |constant struct at -Os vs
                   |                            |-O2
                 CC|                            |marxin at gcc dot gnu.org
             Target|                            |avr

--- Comment #3 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
So this is done at -O2 already but not -Os.  I have not looked into why though.
Someone will need to look at the heurstics to figure out why.

Also it just does not happen on avr even.  There must be some heurstic changes
between most other targets and avr that causes this not to happen.

      parent reply	other threads:[~2021-07-19  3:06 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-11 23:58 [Bug tree-optimization/51506] New: Function cloning misses constant struct peteraward+gcc at gmail dot com
2011-12-12 10:04 ` [Bug tree-optimization/51506] " rguenth at gcc dot gnu.org
2011-12-13  2:21 ` pinskia at gcc dot gnu.org
2021-07-19  3:06 ` pinskia at gcc dot gnu.org [this message]

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-51506-4-xwgHH88FiA@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).