This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: GCSE problem involving mem_first_set.
- To: law at cygnus dot com
- Subject: Re: GCSE problem involving mem_first_set.
- From: Geoff Keating <geoffk at ozemail dot com dot au>
- Date: Tue, 15 Sep 1998 17:30:15 +1000
- CC: egcs-patches at cygnus dot com
- References: <1150.905794562@hurl.cygnus.com>
> Date: Mon, 14 Sep 1998 11:36:02 -0600
> From: Jeffrey A Law <law@cygnus.com>
> > The problem is in GCSE; in the variables mem_first_set and
> > mem_last_set, 0 is used as a flag value meaning 'never set' but 0 can
> > also be a valid CUID. I fixed it by using -1 as the flag value; see
> > patch attached.
> >
> > This should probably be in egcs 1.1.1 if it is ever released.
> Seems to me this would be a whole lot simpler to fix by making the
> first assigned CUID have the value 1.
>
> Any particular reason you didn't do that?
I did consider this (you can just replace i++ by ++i on the
appropriate line). The CUIDs are used to index bit vectors, though,
and since bit vectors are indexed from 0 it seemed reasonable to start
the CUIDs from 0 too.
Feel free to try that instead.
--
Geoffrey Keating <geoffk@ozemail.com.au>