public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "wad at infinet dot ru" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/66090] Wrong loop code generation with -O2 on ARM
Date: Tue, 02 Jun 2015 09:02:00 -0000	[thread overview]
Message-ID: <bug-66090-4-cn5jbL4T81@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-66090-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66090

Andrew <wad at infinet dot ru> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |wad at infinet dot ru

--- Comment #7 from Andrew <wad at infinet dot ru> ---

IMHO

"So no GCC bug, just wrongly assuming pointers can't become null pointers if
they were not null pointers."

Nevertheless, that is no reason to generate an INFINITY LOOP, which will be
cleaned all the memory, including the NULL address.


  parent reply	other threads:[~2015-06-02  9:02 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-10  2:28 [Bug c/66090] New: " christian.prochaska@genode-labs.com
2015-05-10 11:09 ` [Bug c/66090] " kugan at gcc dot gnu.org
2015-05-10 21:43 ` pinskia at gcc dot gnu.org
2015-05-12 19:46 ` rearnsha at gcc dot gnu.org
2015-05-13  8:54 ` rguenth at gcc dot gnu.org
2015-05-13  8:54 ` rguenth at gcc dot gnu.org
2015-05-13 15:20 ` joseph at codesourcery dot com
2015-06-02  9:02 ` wad at infinet dot ru [this message]
2015-06-02  9:07 ` ktkachov at gcc dot gnu.org
2015-06-02  9:13 ` pinskia at gcc dot gnu.org
2015-06-02  9:45 ` wad at infinet dot ru
2015-06-22 18:01 ` mpolacek at gcc dot gnu.org

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-66090-4-cn5jbL4T81@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).