public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/60841] [4.9/4.10 Regression] gcc: internal compiler error: Killed (program cc1) out of memory
Date: Thu, 17 Apr 2014 08:09:00 -0000	[thread overview]
Message-ID: <bug-60841-4-kqUhJba7DC@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-60841-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #14 from Richard Biener <rguenth at gcc dot gnu.org> ---
Author: rguenth
Date: Thu Apr 17 08:09:02 2014
New Revision: 209467

URL: http://gcc.gnu.org/viewcvs?rev=209467&root=gcc&view=rev
Log:
2014-04-17   Richard Biener  <rguenther@suse.de>

    PR tree-optimization/60841
    * tree-vect-data-refs.c (vect_analyze_data_refs): Count stmts.
    * tree-vect-loop.c (vect_analyze_loop_2): Pass down number
    of stmts to SLP build.
    * tree-vect-slp.c (vect_slp_analyze_bb_1): Likewise.
    (vect_analyze_slp): Likewise.
    (vect_analyze_slp_instance): Likewise.
    (vect_build_slp_tree): Limit overall SLP tree growth.
    * tree-vectorizer.h (vect_analyze_data_refs,
    vect_analyze_slp): Adjust prototypes.

    * gcc.dg/vect/pr60841.c: New testcase.

Added:
    trunk/gcc/testsuite/gcc.dg/vect/pr60841.c
Modified:
    trunk/gcc/ChangeLog
    trunk/gcc/testsuite/ChangeLog
    trunk/gcc/tree-vect-data-refs.c
    trunk/gcc/tree-vect-loop.c
    trunk/gcc/tree-vect-slp.c
    trunk/gcc/tree-vectorizer.h


  parent reply	other threads:[~2014-04-17  8:09 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-14 16:58 [Bug c/60841] New: gcc: internal compiler error: Killed (program cc1) in gcc 4.9.0 RC 2014-04-11 mike at vermeulen dot com
2014-04-14 17:01 ` [Bug c/60841] " trippels at gcc dot gnu.org
2014-04-14 17:09 ` trippels at gcc dot gnu.org
2014-04-14 17:13 ` [Bug c/60841] [4.9/4.10 Regression] gcc: internal compiler error: Killed (program cc1) out of memory mike at vermeulen dot com
2014-04-14 17:58 ` trippels at gcc dot gnu.org
2014-04-14 19:23 ` [Bug tree-optimization/60841] " jakub at gcc dot gnu.org
2014-04-15  7:16 ` jakub at gcc dot gnu.org
2014-04-15 13:28 ` jakub at gcc dot gnu.org
2014-04-15 13:41 ` trippels at gcc dot gnu.org
2014-04-15 16:37 ` jakub at gcc dot gnu.org
2014-04-15 16:59 ` jakub at gcc dot gnu.org
2014-04-16  8:35 ` rguenth at gcc dot gnu.org
2014-04-16 12:10 ` rguenth at gcc dot gnu.org
2014-04-16 13:06 ` rguenth at gcc dot gnu.org
2014-04-17  8:09 ` rguenth at gcc dot gnu.org [this message]
2014-04-17  8:10 ` [Bug tree-optimization/60841] [4.9 " rguenth at gcc dot gnu.org
2014-04-22 11:37 ` jakub at gcc dot gnu.org
2014-04-22 13:29 ` rguenth at gcc dot gnu.org
2014-04-22 13:30 ` rguenth 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-60841-4-kqUhJba7DC@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).