This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: i seem to have hit a problem with my new conflict finder.
- From: Ian Lance Taylor <iant at google dot com>
- To: Kenneth Zadeck <zadeck at naturalbridge dot com>
- Cc: "Park, Seongbae" <seongbae dot park at gmail dot com>, "Bergner, Peter" <bergner at vnet dot ibm dot com>, Vladimir Makarov <vmakarov at redhat dot com>, gcc <gcc at gcc dot gnu dot org>
- Date: 17 Aug 2007 07:25:45 -0700
- Subject: Re: i seem to have hit a problem with my new conflict finder.
- References: <46C5A36C.5030704@naturalbridge.com>
Kenneth Zadeck <zadeck@naturalbridge.com> writes:
> There are a lot of ways to handle this problem:
> 1) We could do a pass that breaks multiword sets into individual regs if
> some of those regs are dead. I guess the downside of this is that such
> insns may not match some patterns anymore.
>
> 2) We could turn off local. I was planning on testing this anyway
> because i want to see if local, at this point, is just making global do
> a bad job. However, my hope is that global or the new allocator from
> vlad is smart enough to properly handle the case where some parts of a
> multiword set are dead.
>
> 3) We could fix global/reload to not be stupid. Because, of course,
> you should be able to put something in that unused regs slot.
>
> Any comments.
I think the first step is to figure out what is going wrong. I don't
see any obvious reason why global or reload should fail in this way,
as long as the multi-word set is properly marked as such at the point
of the set itself.
Ian