public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "belagod at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/63679] [5 Regression][AArch64] Failure to constant fold.
Date: Mon, 09 Feb 2015 13:34:00 -0000	[thread overview]
Message-ID: <bug-63679-4-1zpqW7BKt9@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-63679-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #29 from Tejas Belagod <belagod at gcc dot gnu.org> ---
(In reply to rguenther@suse.de from comment #28)
> On Mon, 9 Feb 2015, belagod at gcc dot gnu.org wrote:
> 
> > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63679
> > 
> > --- Comment #27 from Tejas Belagod <belagod at gcc dot gnu.org> ---
> > We'd want to scalarize this early preferably in SRA as it gives a chance to
> > passes like vectorization to vectorize more loops. I checked that
> > sra-max-scalarization-Osize{-Ospeed} had no effect on scalarizing 'a = *.LC0'
> 
> because SRA can't scalarize 'a = *.LC0'.  But yes, ideally we'd change
> gimplification to never decompose initializers but have SRA do it.
> But that's of course not a GCC 5 thing.
> 
> It has the advantage of splitting the initialization only when it is
> (likely) profitable and otherwise leave it to the target to decide
> how to expand the initialization (and it opens up the possibility
> to directly use a constant-pool entry if the data is readonly).

Which cost function(s) control this profitability of early splitting?


  parent reply	other threads:[~2015-02-09 13:34 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-63679-4@http.gcc.gnu.org/bugzilla/>
2014-10-30 10:04 ` [Bug target/63679] [5.0 " belagod at gcc dot gnu.org
2014-10-30 10:10 ` rguenth at gcc dot gnu.org
2014-11-04 11:41 ` belagod at gcc dot gnu.org
2014-11-04 16:32 ` belagod at gcc dot gnu.org
2014-11-04 20:58 ` rguenth at gcc dot gnu.org
2014-11-20 12:44 ` rguenth at gcc dot gnu.org
2014-11-20 16:21 ` belagod at gcc dot gnu.org
2014-11-20 16:49 ` pinskia at gcc dot gnu.org
2014-11-21  8:48 ` rguenth at gcc dot gnu.org
2014-11-21 10:17 ` rguenth at gcc dot gnu.org
2014-11-21 10:26 ` belagod at gcc dot gnu.org
2014-11-21 10:36 ` rguenther at suse dot de
2014-11-21 10:54 ` belagod at gcc dot gnu.org
2014-11-21 11:25 ` jgreenhalgh at gcc dot gnu.org
2014-11-21 18:20 ` jgreenhalgh at gcc dot gnu.org
2014-11-24  8:52 ` rguenther at suse dot de
2014-11-24 11:16 ` belagod at gcc dot gnu.org
2014-11-24 11:31 ` rguenther at suse dot de
2014-11-24 12:01 ` jgreenhalgh at gcc dot gnu.org
2014-11-24 12:19 ` rguenther at suse dot de
2014-11-24 13:45 ` rguenth at gcc dot gnu.org
2014-11-24 13:45 ` rguenth at gcc dot gnu.org
2014-11-24 14:07 ` rguenth at gcc dot gnu.org
2015-02-07 10:55 ` [Bug target/63679] [5 " jakub at gcc dot gnu.org
2015-02-09  9:08 ` rguenth at gcc dot gnu.org
2015-02-09 10:10 ` jakub at gcc dot gnu.org
2015-02-09 12:20 ` belagod at gcc dot gnu.org
2015-02-09 13:17 ` rguenther at suse dot de
2015-02-09 13:34 ` belagod at gcc dot gnu.org [this message]
2015-03-12 16:53 ` [Bug target/63679] [5 / 6 " ramana at gcc dot gnu.org
2015-07-28 17:15 ` [Bug target/63679] [5/6 " alalaw01 at gcc dot gnu.org
2015-07-28 18:36 ` pinskia at gcc dot gnu.org
2015-07-29  7:23 ` rguenther at suse dot de
2015-07-29 17:50 ` alalaw01 at gcc dot gnu.org
2015-08-03 15:38 ` alalaw01 at gcc dot gnu.org
2015-08-04  9:30 ` rguenther at suse dot de

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-63679-4-1zpqW7BKt9@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).