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: Geoff Keating <geoffk at ozemail dot com dot au>
- Subject: Re: GCSE problem involving mem_first_set.
- From: Jeffrey A Law <law at cygnus dot com>
- Date: Mon, 14 Sep 1998 11:36:02 -0600
- cc: egcs-patches at cygnus dot com
- Reply-To: law at cygnus dot com
In message <199809141221.WAA04910@geoffk.wattle.id.au>you write:
>
> The attached short program, "test14.c" (originally part of TeX),
> abort()s when compiled and run on powerpc-unknown-linux-gnu with
>
> gcc -O2 -msdata=sysv test14.c -o test14-exec && ./test14-exec
>
> but not with lower optimisation levels or (annoyingly) without
> -msdata=sysv.
>
> 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?
jeff