public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenther at suse dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/65533] [5 Regression] 252.eon in SPEC CPU 2000 failed to build
Date: Tue, 24 Mar 2015 09:32:00 -0000	[thread overview]
Message-ID: <bug-65533-4-Pxzhod0hnU@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-65533-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #8 from rguenther at suse dot de <rguenther at suse dot de> ---
On Tue, 24 Mar 2015, jakub at gcc dot gnu.org wrote:

> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65533
> 
> --- Comment #7 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
> (In reply to Richard Biener from comment #5)
> > Hmm, looks basically ok, though doing
> > 
> >   vect_free_slp_tree (child);
> > 
> > from the cleanup before
> > 
> >       /* If the SLP build for operand zero failed and operand zero
> >          and one can be commutated try that for the scalar stmts
> >          that failed the match.  */
> >       if (i == 0
> > ...
> > 
> > and simply re-allocating child with
> > 
> >       child = vect_create_new_slp_node (oprnd_info->def_stmts);
> >       if (!child)
> >         {
> >           vect_free_oprnd_info (oprnds_info);
> >           return false;
> >         }
> > 
> > might be "simpler".
> 
> Well, it would be more costly (having to deallocate and allocate everything
> again), and not really much shorter in the source.  Only if we in the future
> popluate early not just the SLP_TREE_CHILDREN vector, but various further
> things your version might be better from maintanance POV.
> 
> > Your patch is ok if it is already tested.
> 
> Not yet tested, but bootstraps/regtests already in progress.  If you feel
> strongly about this, I can surely kill those, write a new patch and redo that.

No, I don't feel strongly about it - for clarity the function should
get some refactoring but not at this stage.


  parent reply	other threads:[~2015-03-24  9:10 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-24  2:19 [Bug middle-end/65533] New: " hjl.tools at gmail dot com
2015-03-24  7:09 ` [Bug middle-end/65533] " hjl.tools at gmail dot com
2015-03-24  7:54 ` jakub at gcc dot gnu.org
2015-03-24  8:00 ` jakub at gcc dot gnu.org
2015-03-24  8:43 ` [Bug tree-optimization/65533] " jakub at gcc dot gnu.org
2015-03-24  8:49 ` jakub at gcc dot gnu.org
2015-03-24  9:10 ` rguenth at gcc dot gnu.org
2015-03-24  9:16 ` rguenth at gcc dot gnu.org
2015-03-24  9:32 ` rguenther at suse dot de [this message]
2015-03-24 10:53 ` jakub at gcc dot gnu.org
2015-03-24 11:43 ` jakub 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-65533-4-Pxzhod0hnU@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).