This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
Re: "[PATCH] cc1/f771 array overrun - x86 Floating Point"
- To: Donn Terry <donnte at microsoft dot com>
- Subject: Re: "[PATCH] cc1/f771 array overrun - x86 Floating Point"
- From: Jeffrey A Law <law at cygnus dot com>
- Date: Wed, 05 Jul 2000 18:37:47 -0600
- cc: "'gcc-bugs at gcc dot gnu dot org'" <gcc-bugs at gcc dot gnu dot org>
- Reply-To: law at cygnus dot com
In message <309F4FC4705DC844987051A517E9E39BF5BCAD@red-pt-02.redmond.corp.mic
rosoft.com>you write:
> This patch reflects an (at least partly) asymtomatic bug. An out of
> bounds array access is occurring with reasonable regularity. In my
> situation, upon occasion the access causes a SIGSEGV, just due to the
> accidents of memory layout. Otherwise, the access appears to be
> benign, in that it seems to have no negative effect that I've detected,
> but since I'm not sure what the variable involved is being used for,
> I can't say for sure.
>
[ ... ]
> (Properly, this should be an ASSERT, but I suspect that it would
> NOT prove a popular choice until the underlying problem is fixed.)
[ ... ]
Make it conditional on ENABLE_CHECKING and make the compiler abort and
it might make sense to include it. At that point it would probably make
sense to include your testcase too.
As for the fix, it may simply be best to call init_insn_lengths after
reg-stack has finished, but I haven't tried it.
jeff