public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/56461] [4.8 Regression] GCC is leaking lots of memory
Date: Fri, 01 Mar 2013 22:55:00 -0000 [thread overview]
Message-ID: <bug-56461-4-svpp6FhJTO@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-56461-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56461
--- Comment #19 from Jakub Jelinek <jakub at gcc dot gnu.org> 2013-03-01 22:54:46 UTC ---
Author: jakub
Date: Fri Mar 1 22:54:39 2013
New Revision: 196396
URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=196396
Log:
PR middle-end/56461
* tree-vect-data-refs.c (vect_permute_store_chain): Avoid using copy
method on dr_chain and result_chain.
* tree-vect-stmts.c (vectorizable_store): Only call
result_chain.create if j == 0.
Modified:
trunk/gcc/ChangeLog
trunk/gcc/tree-vect-data-refs.c
trunk/gcc/tree-vect-stmts.c
next prev parent reply other threads:[~2013-03-01 22:55 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-26 15:47 [Bug middle-end/56461] New: " jakub at gcc dot gnu.org
2013-02-26 15:53 ` [Bug middle-end/56461] " jakub at gcc dot gnu.org
2013-02-26 15:54 ` jakub at gcc dot gnu.org
2013-02-26 15:59 ` jakub at gcc dot gnu.org
2013-02-26 16:01 ` jakub at gcc dot gnu.org
2013-02-26 16:33 ` jakub at gcc dot gnu.org
2013-02-26 20:46 ` vmakarov at gcc dot gnu.org
2013-02-26 21:14 ` jakub at gcc dot gnu.org
2013-02-27 14:02 ` jakub at gcc dot gnu.org
2013-02-27 17:26 ` jakub at gcc dot gnu.org
2013-02-27 21:14 ` steven at gcc dot gnu.org
2013-02-27 21:34 ` jakub at gcc dot gnu.org
2013-02-27 21:35 ` jakub at gcc dot gnu.org
2013-02-27 21:36 ` jakub at gcc dot gnu.org
2013-02-27 21:37 ` jakub at gcc dot gnu.org
2013-02-27 21:41 ` jakub at gcc dot gnu.org
2013-02-27 22:06 ` jakub at gcc dot gnu.org
2013-02-27 22:07 ` jakub at gcc dot gnu.org
2013-02-28 21:21 ` jakub at gcc dot gnu.org
2013-03-01 20:59 ` jakub at gcc dot gnu.org
2013-03-01 21:07 ` jakub at gcc dot gnu.org
2013-03-01 22:55 ` jakub at gcc dot gnu.org [this message]
2013-03-01 22:56 ` jakub at gcc dot gnu.org
2013-03-01 22:57 ` jakub at gcc dot gnu.org
2013-03-04 10:03 ` jakub at gcc dot gnu.org
2013-03-04 10:06 ` jakub at gcc dot gnu.org
2013-03-04 10:08 ` jakub at gcc dot gnu.org
2013-03-04 10:10 ` jakub at gcc dot gnu.org
2013-03-04 21:52 ` jakub at gcc dot gnu.org
2013-03-05 6:03 ` jakub at gcc dot gnu.org
2013-03-05 9:39 ` jakub at gcc dot gnu.org
2013-03-05 9:40 ` jakub at gcc dot gnu.org
2013-03-05 9:40 ` jakub at gcc dot gnu.org
2013-03-05 12:02 ` jakub at gcc dot gnu.org
2013-03-05 15:50 ` jakub at gcc dot gnu.org
2013-03-05 15:52 ` jakub at gcc dot gnu.org
2013-03-05 15:52 ` jakub at gcc dot gnu.org
2013-03-06 16:19 ` 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-56461-4-svpp6FhJTO@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).