This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug c/66090] Wrong loop code generation with -O2 on ARM
- From: "ktkachov at gcc dot gnu.org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Tue, 02 Jun 2015 09:07:11 +0000
- Subject: [Bug c/66090] Wrong loop code generation with -O2 on ARM
- Auto-submitted: auto-generated
- References: <bug-66090-4 at http dot gcc dot gnu dot org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66090
ktkachov at gcc dot gnu.org changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |ktkachov at gcc dot gnu.org
--- Comment #8 from ktkachov at gcc dot gnu.org ---
(In reply to Andrew from comment #7)
> Nevertheless, that is no reason to generate an INFINITY LOOP, which will be
> cleaned all the memory, including the NULL address.
If the program has undefined behaviour, then the compiler makes no guarantees
at all, it's allowed to do pretty much anything at any part of the program