This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: [PATCH]: Handle lonely CC0 setter in sched-deps.c
- From: Hans-Peter Nilsson <hp at bitrange dot com>
- To: Maxim Kuvyrkov <maxim at codesourcery dot com>
- Cc: Paolo Bonzini <bonzini at gnu dot org>, Gabor Loki <loki at gcc dot gnu dot org>, Jim Wilson <wilson at tuliptree dot org>, Vladimir Makarov <vmakarov at redhat dot com>, gcc-patches <gcc-patches at gcc dot gnu dot org>
- Date: Thu, 17 Apr 2008 16:13:40 -0400 (EDT)
- Subject: Re: [PATCH]: Handle lonely CC0 setter in sched-deps.c
- References: <47ECF2BC.1060007@codesourcery.com> <47ECF674.8020900@gnu.org> <47FA03EC.706@codesourcery.com> <20080408072944.A44042@dair.pair.com> <48077672.2010901@codesourcery.com>
On Thu, 17 Apr 2008, Maxim Kuvyrkov wrote:
> Hans-Peter Nilsson wrote:
> > This looks much too conservative. I had a loook and ISTM it'd
> > be better to fix rtl-factoring.c:matching_length to make sure
> > cc0 setter and users (must be the next_nonnote_insn) are *both*
> > (or neither) added to such a sequence.
>
> I agree, but. I don't think it's worth adding any extensive support for CC0,
> which is being deprecated.
The fix I hint above would be shorter and simpler than the one
you suggested in
<http://gcc.gnu.org/ml/gcc-patches/2008-04/msg00528.html> so
that's not an argument.
> > Can you please enter a bugzilla report for your original bug?
> > I'll have a look as I'm interested in making scheduling work for
> > CRIS (currently a cc0 target).
>
> The bug occurs only with the patch for scheduling for ColdFire, which is not
> yet committed to mainline. So submitting the bug report would be rather
> meaningless.
Another reason is that I'd like to know if I can trig it by
adding scheduling to the CRIS port. What happens when the bug
trigs; what's the ICE error message?
brgds, H-P