This is the mail archive of the
mailing list for the GCC project.
Re: ACATS c380004
- From: Duncan Sands <duncan dot sands at math dot u-psud dot fr>
- To: kenner at vlsi1 dot ultra dot nyu dot edu (Richard Kenner)
- Cc: gcc at gcc dot gnu dot org
- Date: Mon, 10 Jan 2005 21:16:12 +0100
- Subject: Re: ACATS c380004
- References: <10501071528.AA15192@vlsi1.ultra.nyu.edu>
> Right. It's trying to allocate an amount of memory that overflows because
> it thinks it needs to allocate an array of 2**32 entries. This can either
> end up allocating zero bytes, a negative number, or a large positive
> number depending on lot of random things.
what I don't understand is: why does it need to allocate so much memory?
I've looked through the test and at first glance it looks perfectly harmless.
What is more, gcc at the pre-ssa tag allocates only mild amounts of memory,
does not try to access unallocated memory (according to valgrind), and passes
the test. This seems to indicate that vast quantities of memory are not needed.
Is it really succeeding by accident as you seem to suggest?
All the best,