This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug tree-optimization/37916] [4.3/4.4/4.5/4.6 Regression] SSA names causing register pressure; unnecessarily many simultaneously "live" names.
- From: "steven at gcc dot gnu.org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Sat, 5 Mar 2011 00:18:48 +0000
- Subject: [Bug tree-optimization/37916] [4.3/4.4/4.5/4.6 Regression] SSA names causing register pressure; unnecessarily many simultaneously "live" names.
- Auto-submitted: auto-generated
- References: <bug-37916-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=37916
Steven Bosscher <steven at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |steven at gcc dot gnu.org
--- Comment #19 from Steven Bosscher <steven at gcc dot gnu.org> 2011-03-05 00:18:29 UTC ---
(In reply to comment #11)
> (In reply to comment #10)
> > Is scheduling before reload enabled for your target? If not can you try
> > -fschedule-insns1?
>
> No such option, I presume you mean -fschedule-insns. But, as there's no
> scheduler description defined for the architecture, all I get is of course:
> warning: instruction scheduling not supported on this target machine
> with no difference in the output with -O2 -march=v10 -mno-mul-bug-workaround
> -fno-ivopts -fno-reorder-blocks -fno-gcse.
>
> Besides, scheduling would move uses away from definitions, not closer to them.
> :) Also, if this is meant as a permanent solution, that pass seems a bit late.
Random thought on this PR: With a scheduler description, -fschedule-insns
-fsched-pressure may help.
Is there a reason why there is no scheduler description?