public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/67651] Optimizer assumes nothing can reside at address 0 despite -fno-delete-null-pointer-checks Date: Mon, 21 Sep 2015 12:33:00 -0000 [thread overview] Message-ID: <bug-67651-4-90EgM9rSjG@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-67651-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67651 --- Comment #4 from Richard Biener <rguenth at gcc dot gnu.org> --- Author: rguenth Date: Mon Sep 21 12:33:23 2015 New Revision: 227968 URL: https://gcc.gnu.org/viewcvs?rev=227968&root=gcc&view=rev Log: 2015-09-21 Richard Biener <rguenther@suse.de> PR middle-end/67651 * rtlanal.c (nonzero_address_p): SYMBOL_REFs may have zero address with -fno-delete-null-pointer-checks. Modified: trunk/gcc/ChangeLog trunk/gcc/rtlanal.c
prev parent reply other threads:[~2015-09-21 12:33 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-09-20 16:14 [Bug c/67651] New: " soren.brinkmann at xilinx dot com 2015-09-20 16:19 ` [Bug c/67651] " soren.brinkmann at xilinx dot com 2015-09-21 8:06 ` [Bug middle-end/67651] " rguenth at gcc dot gnu.org 2015-09-21 12:33 ` rguenth at gcc dot gnu.org 2015-09-21 12:33 ` rguenth at gcc dot gnu.org [this message]
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-67651-4-90EgM9rSjG@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: linkBe 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).