--- Comment #9 from wilson at gcc dot gnu dot org 2010-04-21 05:31 ---
Fixed on mainline.
--
wilson at gcc dot gnu dot org changed:
What|Removed |Added
Status
--
wilson at gcc dot gnu dot org changed:
What|Removed |Added
AssignedTo|unassigned at gcc dot gnu |wilson at gcc dot gnu dot
|dot org
--- Comment #8 from wilson at gcc dot gnu dot org 2010-04-21 05:29 ---
Subject: Bug 43520
Author: wilson
Date: Wed Apr 21 05:29:11 2010
New Revision: 158584
URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=158584
Log:
PR rtl-optimization/43520
* ira-lives.c (ira_implicitly_set_ins
--- Comment #7 from wilson at gcc dot gnu dot org 2010-04-20 01:17 ---
Subject: Bug 43520
Author: wilson
Date: Tue Apr 20 01:16:59 2010
New Revision: 158539
URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=158539
Log:
partial fix, make all 'e' class regs fixed
PR rtl-optimization/
--- Comment #6 from wilson at gcc dot gnu dot org 2010-04-14 21:59 ---
Created an attachment (id=20381)
--> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=20381&action=view)
untested patch that works for testcase
This is logically 3 different patches that can be handled separately. Th
--- Comment #5 from wilson at gcc dot gnu dot org 2010-04-14 21:57 ---
I think the first part of the solution here is to make ira stop handling
zero-size classes as ones that have a potential register pressure problem.
The second part, is that I think we can make ar.lc a fixed register.
--- Comment #4 from wilson at gcc dot gnu dot org 2010-03-30 23:58 ---
I've confirmed that Vlad's -fsched-pressure patch is the problem, and done a
bit more analysis to see why.
The testcase has approximately 20,000 movdi_internal insns, 6000 movsi_internal
insns, and 10,000 call_value_
--- Comment #3 from wilson at codesourcery dot com 2010-03-25 23:21 ---
Subject: Re: gcc.dg/pr43058.c uses way too
memory on ia64
On Thu, 2010-03-25 at 19:05 +, pinskia at gcc dot gnu dot org wrote:
> Did you test earlier versions of GCC with the testcase?
I hadn't gotten around
--- Comment #2 from pinskia at gcc dot gnu dot org 2010-03-25 19:05 ---
Did you test earlier versions of GCC with the testcase?
Also it should not hard to figure out where in the scheduler the memory is
being used. The kernel panic is not our fault so make sure the kernel guys get
a bu
