This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug optimization/13828] access to local array in while loop is optimized away
- From: "a dot simon at kent dot ac dot uk" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 23 Jan 2004 17:18:07 -0000
- Subject: [Bug optimization/13828] access to local array in while loop is optimized away
- References: <20040123095739.13828.a.simon@kent.ac.uk>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Additional Comments From a dot simon at kent dot ac dot uk 2004-01-23 17:18 -------
Subject: Re: access to local array in while loop is optimized away
On Fri, Jan 23, 2004 at 04:19:34PM -0000, pinskia at gcc dot gnu dot org wrote:
>
> ------- Additional Comments From pinskia at gcc dot gnu dot org 2004-01-23 16:19 -------
> Can you stop opening a new bug for an invalid bug.
> This is invalid as you are incrementing and acessing current without going through a sequence
> point:
> localArray[current]=localArray[++current];
> This is undefined.
> This can be evaluated as:
> current++;
> localArray[current]=localArray[current];
> or
> temp = & localArray[current];
> current++;
> *temp = localArray[current];
I did understand the first explaination and felt stupid enough. I
wasn't aware of having reopened the bug on bugzilla. In fact I am quite
positive that I didn't click on reopen, let alone commit. Maybe I reloaded
the submission page?!
Sorry about that,
Axel.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=13828